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
- 13
- Versions published
- 4
- First published
- Feb 2026
- Publisher
- spotify-eng
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":["@spotify/[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":["@spotify/[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
buildbackstage-cli package build --minifycleanbackstage-cli package cleanlintbackstage-cli package lint --max-warnings 0postpackbackstage-cli package postpackprepackbackstage-cli package prepacktestbackstage-cli package test
Dependencies7
@backstage/backend-plugin-api^1.9.1@backstage/catalog-client^1.15.1@backstage/config^1.3.8@backstage/plugin-catalog-node^2.2.1@google-cloud/bigquery^8.0.0@spotify/backstage-plugin-soundcheck-node^0.14.0knex^3.0.0