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.

Versions published: 24Mature · −50% score
First published: Apr 2025
Publisher: jjeett0007

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 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":["[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"}'

Publisherjjeett0007

Artifact bytes260,737

Previous version1.6.3

Published2026-06-13T07:32:56.474Z

SHA-256a7c7256a5ecfaaa29d86dae02d61e498d432af494b4a9c5701cfbdedae1f9e17

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

20h agoLast checked

reviewRisk

2Score

2.0.0Version

Status history (1 event)

new → available20h ago · risk review · score 2 · status changed

Evidence

Static findings

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

No high-signal findings — see all findings below.

Show all 3 findings (low-signal and informational)

Severity	Kind	Path	Detail	Points
low	Credential file access	package/template/typescript-with-prisma/src/lib/s3.ts	matched "AWS_ACCESS_KEY"	5
low	Obfuscation Density	package/template/typescript/package-lock.json	high encoded/escaped-token density	0
low	Obfuscation Density	package/template/typescript-with-prisma/pnpm-lock.yaml	high encoded/escaped-token density	0

Manifest

Package metadata

Scripts6

buildtsc
devnodemon
drop-indexnode scripts/dropPassIdIndex.js
killpm2 kill
startpm2 start ecosystem.config.json --no-daemon
testjest --runInBand

Dependencies32

@sentry/node^10.22.0
@sentry/profiling-node^10.22.0
@sentry/tracing^7.120.4
aws-sdk^2.1692.0
bcryptjs^3.0.2
cors^2.8.5
cross-env^7.0.3
dicer^0.3.1
dotenv^16.6.1
express^4.18.2
express-session^1.18.1
firebase^10.7.1
http^0.0.1-security
http-status^1.7.3
joi^17.11.0
jsonwebtoken^9.0.2
moment^2.30.1
mongoose^8.0.3
morgan^1.10.0
nock^14.0.9
node-cron^3.0.3
nodemailer^6.9.7
nodemon^3.0.2
passport^0.7.0
passport-google-oauth2^0.2.0
passport-google-oauth20^2.0.0
path^0.12.7
swagger-jsdoc^6.2.8
swagger-ui-express^5.0.0
tslib^2.8.1
…and 2 more.