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
- 15
- Versions published
- 31
- First published
- Apr 2026
- Publisher
- bianpratama
Recommended action
Looks clean — keep monitoringNo high-signal indicators in the stored static report. PkgRadar will re-check on the next ingest pass.
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":["@prata.ma/[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":["@prata.ma/[email protected]"],"fail_on":"review"}'Why flagged
What the scanner saw
No high-signal static finding in the saved report.
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 low · score 0 · status changed
Evidence
Static findings
No findings stored for this release.
Manifest
Package metadata
Scripts6
buildtsdown && node ./scripts/postbuild.mjslinteslint .lint:fixeslint . --fixrelease:checkpnpm build && pnpm lint && pnpm test && pnpm test:typetestvitest run --passWithNoTeststest:typetsc --noEmit
Dependencies14
@changesets/changelog-github^0.7.0@clack/prompts^1.5.0@notionhq/client^5.22.0@prata.ma/anvil-schema3.0.3citty^0.2.2confbox^0.2.4execa^9.6.1picocolors^1.1.1remark-parse^11.0.0remark-stringify^11.0.0unified^11.0.5unist-util-visit^5.1.0xdg-basedir^5.1.0yaml^2.9.0