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
- 23
- Versions published
- 10
- First published
- Apr 2026
- Publisher
- graysonlang
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":["@graysonlang/[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":["@graysonlang/[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
Scripts11
buildnode ./scripts/build.mjs --lint --minifycert:devESP_DEV_CERT_NAME=$npm_package_config_esp_dev_cert_name esp-generate-dev-certdevnpm run serve -- --proxy --launchdev:httpsnpm run serve:https -- --proxy --launchlinteslint . --ignore-pattern 'dist'servenode ./scripts/build.mjs --lint --sourcemap --watch --serve --debug-port=9222serve:httpsESP_DEV_CERT_NAME=$npm_package_config_esp_dev_cert_name npm run serve -- --host=0.0.0.0 --port=8443testecho "Error: no test specified" && exit 1vscode:buildnpm run build -- --vscodevscode:debugnpm run serve -- --vscodevscode:debug:httpsnpm run serve:https -- --vscode