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
- 277
- Versions published
- 9
- First published
- May 2026
- Publisher
- lekhang4497
Recommended action
Block this updateStatic evidence trips multiple high-signal indicators. Quarantine the release until the publisher validates the change or you can rule out the indicators below.
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":"high"}'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":"high"}'Why flagged
What the scanner saw
Credential File Packaged: package/dist/.env
Not observed: package install, lifecycle script execution, or sandbox execution. PkgRadar only inspects on-disk artifacts.
Availability ledger
available
Status history (1 event)
- new → available · risk high · score 40 · status changed
Evidence
Static findings
2 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Credential File Packaged | package/dist/.env | package/dist/.env | 35 |
Show all 2 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| high | Credential File Packaged | package/dist/.env | package/dist/.env | 35 |
| low | Credential file access | package/dist/.next/server/app/api/oauth/kiro/auto-import/route.js | matched ".aws/" | 5 |
Manifest
Package metadata
Scripts13
buildNODE_ENV=production next build --webpackbuild:bunNODE_ENV=production bun --bun next build --webpackdevnext dev --webpack --port 20129dev:bunbun --bun next dev --webpack --port 20128electron:buildnext build && electron-builder --config electron/builder.jsonelectron:devconcurrently -k -n NEXT,ELECTRON -c blue,magenta "next dev --webpack --port 20129" "wait-on http://127.0.0.1:20129 && electron electron/main.js"electron:packnext build && electron-builder --config electron/builder.json --dirpack:assemblenode scripts/pack-assemble.jspostpacknode scripts/publish-pkg.js restoreprepacknode scripts/pack-assemble.js && node scripts/publish-pkg.js trimstartNODE_ENV=production next startstart:bunNODE_ENV=production bun ./.next/standalone/server.jstypechecktsc --noEmit