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
- 38
- First published
- May 2026
- Publisher
- orgcarlosn
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":["@imolko/[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":["@imolko/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Credential file access: matched ".npmrc"
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 10 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Credential file access | package/bin/commands/build.js | matched ".npmrc" | 10 |
Manifest
Package metadata
Scripts2
build[ -d bin ] && rm -r bin; tsc --project tsconfig.build.json && cp -r src/reporters/templates bin/reporters/templates && chmod +x ./bin/cli.jstestjest
Dependencies10
@imolko/ultra-tsconfig^1.1.0better-docs^2.7.3chalk^5.6.2commander^14.0.3jest-html-reporters^3.1.7js-yaml^4.1.1jsdoc^4.0.5simply-beautiful^1.0.1typescript^6.0.3winston^3.19.0