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
- 25
- First published
- Mar 2026
- Publisher
- chiefmikey
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":["@depup/[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":["@depup/[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
Dependencies18
estree-util-value-to-estree^3.5.0github-slugger^2.0.0hast-util-to-estree^3.1.3hast-util-to-jsx-runtime^2.3.6mdast-util-mdx^3.0.0mdast-util-to-markdown^2.1.2npm-to-yarn3.2.0remark^15.0.1remark-gfm^4.0.1remark-rehype^11.1.2scroll-into-view-if-needed^3.1.0shiki^4.4.2tinyglobby^0.2.17unified^11.0.5unist-util-visit^5.1.0vfile^6.0.3yaml^2.9.0zbsearch^3.3.4