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
- 26
- Versions published
- 8
- First published
- Oct 2024
- Publisher
- alanscodelog
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":["@alanscodelog/[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":["@alanscodelog/[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
Scripts6
buildvite buildlintpnpm lint:types && pnpm lint:commitslint:commitscommitlint --from-last-tag --to HEAD --verboselint:typestsc --noEmit --prettyplaycd playground && vite buildtestecho no tests
Dependencies9
@alanscodelog/commitlint-config^3.1.2@alanscodelog/semantic-release-config^6.0.0@alanscodelog/tsconfigs^6.2.0@commitlint/cli^20.1.0defu^6.1.4fast-glob^3.3.3vite^7.2.4vite-plugin-externalize-deps^0.10.0vitest^4.0.14