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
- 3
- First published
- Jun 2026
- Publisher
- trankimhieu
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":["@nivoai/[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":["@nivoai/[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
Scripts4
buildtsc -blinteslint srctestvitest run --passWithNoTeststypechecktsc --noEmit -p tsconfig.json
Dependencies19
@ai-sdk/anthropic3.0.81@ai-sdk/openai3.0.68@mozilla/readability0.6.0@napi-rs/keyring1.3.0@secretlint/core13.0.2@secretlint/node13.0.2@secretlint/secretlint-rule-preset-recommend13.0.2@secretlint/source-creator13.0.2ai6.0.197async-mutex0.5.0env-paths4.0.0ipaddr.js2.4.0isomorphic-git1.38.4linkedom0.18.12mammoth1.12.0ulidx2.4.1undici6.26.0unpdf1.6.2zod4.4.3