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
- 8
- First published
- Feb 2024
- Publisher
- coder-bot
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":["@coder/[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":["@coder/[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
Scripts8
buildbackstage-cli package buildcleanbackstage-cli package cleanlintbackstage-cli package lintpostpackbackstage-cli package postpackprepackbackstage-cli package prepackstartbackstage-cli package starttestbackstage-cli package testtest:typestsc --noEmit
Dependencies10
@backstage/core-components^0.13.10@backstage/core-plugin-api^1.8.2@backstage/integration-react^1.1.24@backstage/plugin-catalog-react^1.10.0@backstage/theme^0.5.0@material-ui/core^4.12.2@material-ui/icons^4.9.1@material-ui/lab4.0.0-alpha.61@tanstack/react-query4.36.1valibot^0.28.1