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
- 14
- Versions published
- 7
- First published
- May 2026
- Publisher
- luizfosc
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":["@luizfosc/[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":["@luizfosc/[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
Scripts8
doctornode bin/forge.js doctorformatprettier --write "src/**/*.{js,json,md}" "bin/**/*.js"linteslint src/ bin/ hooks/testvitest runtest:coveragevitest run --coveragetest:watchvitesttypechecktsc --noEmit --allowJs --checkJs src/**/*.jsverify-no-absolute-paths! grep -rE '/Users/|/home/' src/ bin/ hooks/ 2>/dev/null
Dependencies5
@clack/prompts^0.7.0ajv^8.12.0fast-json-patch^3.1.1js-yaml^4.1.0kleur^4.1.5