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
- 111
- Versions published
- 128Mature · −50% score
- First published
- May 2022
- Publisher
- atrouw
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 promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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":["@xylabs/[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":["@xylabs/[email protected]"],"fail_on":"review"}'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
Status history (1 event)
- new → available · risk review · score 5 · status changed
Evidence
Static findings
2 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 2 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/dist/node/index.mjs | matched "AWS_ACCESS_KEY" | 5 |
| low | Credential file access | package/dist/node/bin/start-meta.mjs | matched "AWS_ACCESS_KEY" | 5 |
Manifest
Package metadata
Scripts6
benchNODE_OPTIONS=--max-old-space-size=2048 vitest bench --runbuild-teststsc --noEmit --lib dom,esnextcoveragepnpm vitest --coveragestartnodemonstart-esmnode ./dist/node/bin/start-meta.mjstestvitest run
Dependencies17
@aws-sdk/client-s3~3.1068.0@xylabs/express~6.1.1@xylabs/sdk-js~6.1.1@xylabs/sdk-meta~6.1.1@xyo-network/axios~2.91.3async-mutex~0.5.0axios~1dotenv~17.4.2express~5.2.1he~1.2.0http-status-codes~2.3.0lru-cache~11.5.1mime~4.1.0minimatch~10.2.5puppeteer~25.1.0serve-static~2.2.1yargs~18.0.0