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
- 12
- First published
- Jan 2026
- Publisher
- setonix
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":["@developer-overheid-nl/[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":["@developer-overheid-nl/[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
Scripts 3
Sign in to view install / lifecycle script contents.
Dependencies12
@developer-overheid-nl/don-register-locales1.0.0@piwikpro/react-piwik-pro2.5.0@rijkshuisstijl-community/components-css12.0.0@rijkshuisstijl-community/components-react11.0.0@rijkshuisstijl-community/design-tokens11.0.0@types/parse-link-header^2.0.3clsx2.1.1i18next25.8.4parse-link-header^2.0.0react-i18next16.5.4react-markdown10.1.0remark-behead^3.1.0