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
- May 2026
- Publisher
- isaiahiroko
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":["@thescaffold/[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":["@thescaffold/[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
Scripts4
buildtsupdevtsup --watchtestvitest runtypechecktsc --noEmit
Dependencies18
@aws-sdk/client-s3^3.1047.0@aws-sdk/s3-request-presigner^3.1047.0@swc/core^1.15.33@types/dompurify^3.0.5@types/jsdom^28.0.3@types/markdown-it^14.1.2@types/pg^8.20.0dompurify^3.4.3ioredis^5.10.1ioredis-mock^8.13.1jose^5.10.0jsdom^25.0.1markdown-it^14.1.1pg^8.20.0pino^9.14.0prom-client^15.1.3reflect-metadata^0.2.2typeorm^0.3.29