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
- 9
- First published
- Nov 2021
- Publisher
- shyam-builder
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":["@builder.io/[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":["@builder.io/[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
Scripts3
buildtsc && rollup --silent -creleasenpm run build && npm version patch && npm publishtsctsc
Dependencies12
@builder.io/sdk^1.1.23@rollup/plugin-commonjs^15.1.0@rollup/plugin-node-resolve^9.0.0@rollup/plugin-typescript^6.0.0@sentry/browser^6.15.0@types/amplitude-js^6.0.0@types/lodash^4.14.177amplitude-js^7.2.2rollup^2.29.0rollup-plugin-terser^7.0.2tslib^2.0.3typescript4.6.3