Package evidence

@dotenc/[email protected]

Credential file access: matched "id_rsa"

Trust signals

Why this verdict

PkgRadar discounts a release’s score when public reputation argues against novel malware. The verdict above already reflects these — the panel just explains what was applied.

Versions published: 36Mature · −50% score
First published: Mar 2025
Publisher: GitHub ActionsTrusted automation · −70% score

Effective trust discount applied: −70% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.

Recommended action

Review before promoting

Mixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.

Inspect tarball Add to CI gate

Block this release in CIcurl · GitHub Actions

Fail the build when this package version is added or upgraded. Replace $PKGRADAR_TOKEN with a Pro / Team API key from your dashboard.

curl -fsS https://pkgradar.com/gate/npm \
  -H "Authorization: Bearer $PKGRADAR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"specs":["@dotenc/[email protected]"],"fail_on":"review"}'

GitHub Actions step:

- name: PkgRadar gate
  run: |
    curl -fsS https://pkgradar.com/gate/npm \
      -H "Authorization: Bearer ${{ secrets.PKGRADAR_TOKEN }}" \
      -H "Content-Type: application/json" \
      -d '{"specs":["@dotenc/[email protected]"],"fail_on":"review"}'

PublisherGitHub Actions

Artifact bytes33,918

Previous version0.7.7

Published2026-03-02T02:49:15.383Z

SHA-256a2d608bf3353b14ff54b3ffcab7baa7954e08fee8f2e8366c826a12eb26eac49

Why flagged

What the scanner saw

Credential file access: matched "id_rsa"

Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.

Availability ledger

available

review

6h agoLast checked

reviewRisk

1Score

0.8.0Version

Status history (1 event)

new → available6h ago · risk review · score 1 · status changed

Evidence

Static findings

1 static · 0 from release diff · showing high-signal first.

No high-signal findings — see all findings below.

Show all 1 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
low	Credential file access	package/dist/cli.js	matched "id_rsa"	5

Manifest

Package metadata

Scripts14

buildbun build src/cli.ts --outdir dist --target node --packages external
build:binarybun run build:binary:darwin-arm64 && bun run build:binary:darwin-x64 && bun run build:binary:linux-x64 && bun run build:binary:linux-arm64 && bun run build:binary:windows-x64
build:binary:darwin-arm64bun build src/cli.ts --compile --target=bun-darwin-arm64 --outfile dist/dotenc-darwin-arm64
build:binary:darwin-x64bun build src/cli.ts --compile --target=bun-darwin-x64 --outfile dist/dotenc-darwin-x64
build:binary:linux-arm64bun build src/cli.ts --compile --target=bun-linux-arm64 --outfile dist/dotenc-linux-arm64
build:binary:linux-x64bun build src/cli.ts --compile --target=bun-linux-x64 --outfile dist/dotenc-linux-x64
build:binary:windows-x64bun build src/cli.ts --compile --target=bun-windows-x64 --outfile dist/dotenc-windows-x64
devbun src/cli.ts
startnode dist/cli.js
testbun test
test:coveragebun test src/tests --coverage --coverage-reporter lcov --coverage-dir coverage
test:e2edocker build -t dotenc-e2e -f e2e/Dockerfile .. && docker run --rm dotenc-e2e
test:e2e:coveragerm -rf coverage-e2e && mkdir -p coverage-e2e && docker build -t dotenc-e2e -f e2e/Dockerfile .. && docker build -t dotenc-e2e-coverage -f e2e/Dockerfile.coverage .. && docker run --rm -v "$(pwd)/coverage-e2e:/cov" dotenc-e2e-coverage
typechecktsc --noEmit -p tsconfig.json

Dependencies5

chalk^5.4.1
commander^13.1.0
eciesjs^0.4.15
inquirer^12.4.2
zod^3.24.2