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
- Jul 2024
- Publisher
- simonfan
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":["@orioro/[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":["@orioro/[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
Scripts1
buildrollup --config ./rollup.config.mjs
Dependencies17
@babel/preset-env^7.23.9@babel/preset-react^7.23.3@babel/preset-typescript^7.23.3@rollup/plugin-babel^6.0.4@rollup/plugin-commonjs^25.0.7@rollup/plugin-json^6.1.0@rollup/plugin-node-resolve^15.2.3@rollup/plugin-typescript^11.1.6@storybook/addon-essentials^8.0.0@storybook/addon-interactions^8.0.0@storybook/nextjs^8.0.0@storybook/test^8.0.0rollup^4.13.0rollup-plugin-import-css^3.5.0storybook^8.0.0typescript^5.3.3webpack5.101.2