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
- 1
- First published
- Jun 2026
- Publisher
- codemeall
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":["@codemeall/[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":["@codemeall/[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
Scripts7
buildnpm run prepare:content && npm run quartz:install && node scripts/run-quartz.mjs build -d ../quartz-content -o publicimport:jekyllnode scripts/import-jekyll-posts.mjsprepare:contentnode scripts/prepare-quartz-content.mjspreviewnpm run prepare:content && npm run quartz:install && node scripts/run-quartz.mjs build -d ../quartz-content --servequartz:installnode scripts/install-quartz.mjstestnode --testwizardvite --host 127.0.0.1 --config wizard/vite.config.ts
Dependencies4
@vitejs/plugin-react^5.0.0react^19.0.0react-dom^19.0.0vite^7.0.0