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
- 1,268Mature · −50% score
- First published
- Apr 2024
- Publisher
- bassel17
Effective trust discount applied: −50% (max across signals — discounts don’t stack). New install-lifecycle deltas vs the previous release would clear the discount.
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":["@strapi/[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":["@strapi/[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
Scripts5
buildpack-up buildcleanrun -T rimraf ./distlintrun -T eslint .test:unitrun -T jestwatchpack-up watch
Dependencies19
@strapi/utils4.26.2axios1.15.2chalk4.1.2cli-progress3.12.0commander8.3.0eventsource2.0.2fast-safe-stringify2.1.1fs-extra10.0.0inquirer8.2.5jsonwebtoken9.0.0jwks-rsa3.1.0lodash4.18.1minimatch9.0.3open8.4.0ora5.4.1pkg-up3.1.0tar7.5.7xdg-app-paths8.3.0yup0.32.9