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
- 65
- First published
- May 2026
- Publisher
- 58bits
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":["@byline/[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":["@byline/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
Remote Payload: matched "cUrl "
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 12 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| medium | Remote Payload | package/dist/s3-storage-provider.js | matched "cUrl " | 12 |
Manifest
Package metadata
Scripts6
buildtsc -p tsconfig.json && tsc-aliascleannode scripts/clean.js node_modules dist build .turbodevchokidar 'src/**/*' -c 'npm-run-all build'lintbiome check --write --unsafe --diagnostic-level=errorskiptsx ./scripts/task-watch.jstypechecktsc --noEmit
Dependencies5
@aws-sdk/client-s3^3.1053.0@aws-sdk/lib-storage^3.1053.0@byline/core2.4.4npm-run-all^4.1.5uuid^14.0.0