PkgRadar

Package evidence

[email protected]

Credential file access: matched "aws_access_key"

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.

Weekly downloads
280
Versions published
304Mature · −50% score
First published
Jun 2024
Publisher
enestufekci

Effective trust discount applied: −50% (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 tarballAdd 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":["[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":["[email protected]"],"fail_on":"review"}'
Publisherenestufekci
Artifact bytes3,932,275
Previous version0.36.1
Published2026-05-18T15:14:49.570Z
SHA-2565ea67cc38ac5a43c5fc72b909338724fbd09db2c66f82a202f05c63afa795cbe

Why flagged

What the scanner saw

Credential file access: matched "aws_access_key"

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

Availability ledger

available

review
Last checked
reviewRisk
7Score
0.36.2Version
Status history (1 event)
  1. new → available · risk review · score 7 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 4 findings (low-signal and informational)
SeverityKindPathDetailPoints
lowCredential file accesspackage/dist/chunk-fjqa7s60.jsmatched "aws_access_key"5
lowCredential file accesspackage/dist/chunk-njyeb40r.jsmatched "AWS_ACCESS_KEY"5
lowCredential file accesspackage/dist/chunk-txk5dr5r.jsmatched "AWS_ACCESS_KEY"5
lowObfuscation Densitypackage/dist/chunk-abmx623n.jshigh encoded/escaped-token density0

Manifest

Package metadata

Scripts11
  • buildNODE_ENV=production bun run build:core && bun run build:bin && bun run build:types && bun run build:client && bun run build:plugin && bun run build:client-types
  • build:binbun build --outdir=./dist/bin --target=bun --external=vite --external=react-dom --external=react/jsx-runtime --external=bun --external=sharp --sourcemap ./bin/gemi.ts && bun ./scripts/prepare-bin.ts
  • build:clientvite build -c vite.client.config.mts
  • build:client-typestsc -p tsconfig.browser.json
  • build:corebun ./scripts/build.ts
  • build:pluginvite build -c vite.plugin.config.mts
  • build:typestsc
  • lintoxlint
  • postpublishbun scripts/setupExports.ts dev
  • prepublishOnlybun run build && bun scripts/setupExports.ts prod
  • testvitest
Dependencies20
  • @aws-sdk/client-s3^3.629.0
  • @aws-sdk/s3-request-presigner^3.629.0
  • @prisma/client^6.4.1
  • ast-types^0.14.2
  • commander^12.1.0
  • cronbake^0.1.2
  • history^5.3.0
  • jsx-email2.0.0-rc2.1
  • open^10.1.0
  • react19.2.3
  • react-dom19.2.3
  • react-error-boundary^6.0.0
  • recast^0.23.9
  • resend^6.12.3
  • satori^0.12.2
  • temporal-polyfill^0.2.5
  • twitter-api-v2^1.20.2
  • urlpattern-polyfill^10.0.0
  • uuid^9.0.1
  • vite^6.3.5