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
- Jun 2026
- Publisher
- luiscortesdev
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":["@luiscortesdev/[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":["@luiscortesdev/[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
buildrimraf dist && tsc && cpy "src/templates/**/*" dist/templatesdevtsx src/index.tstestvitest
Dependencies18
chalk^5.6.2chokidar^3.6.0commander^14.0.3crypto^1.0.1fs-extra^11.3.4gray-matter^4.0.3inquirer^13.3.0nunjucks^3.2.4rehype-document^7.0.3rehype-raw^7.0.0rehype-stringify^10.0.1remark-gfm^4.0.1remark-parse^11.0.0remark-rehype^11.1.2unified^11.0.5unist-util-visit^5.1.0ws^8.19.0zod^4.3.6