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
- 2
- First published
- Jun 2026
- Publisher
- specificshen
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":["@spcsn/[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":["@spcsn/[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
buildpnpm run clean && tsc && pnpm run copy:templatecleanbun ../../scripts/clean.ts distcopy:templatebun ./scripts/copy-template.tsdevpnpm run copy:template && tsc -wprodpnpm run build
Dependencies19
@spcsn/taro-helper1.0.1@spcsn/taro-runtime1.0.1@spcsn/taro-shared1.0.1@vitejs/plugin-react^6.0.2acorn^8.11.3acorn-walk^8.3.2autoprefixer^10.4.19html-minifier^4.0.0lodash^4.17.21picomatch^4.0.2postcss^8.5.6react^19.2.0react-dom^19.2.0react-reconciler0.33.0regenerator-runtime0.11sax1.2.4terser^5.30.4vite^8.0.13vite-plugin-static-copy^4.1.0