Package evidence
[email protected]
Suspicious Publish Context: {"package_age_days":2,"publisher":"zarve","burst_same_day":0,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}
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
- 2
- First published
- Jun 2026
- Publisher
- zarve
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":["[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"}'Why flagged
What the scanner saw
Suspicious Publish Context: {"package_age_days":2,"publisher":"zarve","burst_same_day":0,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true}
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 | Suspicious Publish Context | manifest | {"package_age_days":2,"publisher":"zarve","burst_same_day":0,"burst_week":1,"lure":null,"version_anomaly":false,"new_account":true} | 10 |
Manifest
Package metadata
Scripts9
buildtsc -p tsconfig.serde.json && tsc-alias -p tsconfig.serde.json --resolve-full-pathsdev:generatetsx serde/cli.ts generatedev:inittsx serde/cli.ts initpack:drynpm pack --dry-runprepacknpm run buildtestnpm run test:generate && npm run test:asc && npm run test:nodetest:ascasc tests/assembly/index.ts --target debug --outFile tests/build/debug.wasm --bindings esmtest:generatetsx serde/cli.ts generate --config tests/as-borsh.test.config.jsonctest:nodenode --test tests/index.js
Dependencies1
jsonc-parser^3.3.1