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
- 19
- First published
- Apr 2026
- Publisher
- noalia.dev
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":["@noalia/[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":["@noalia/[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
buildnpm run clean && node ./scripts/run-tsc.jscleannode -e "require('fs').rmSync('dist', { recursive: true, force: true })"devnode ./scripts/run-tsc.js --watchprepacknpm run buildprepublishOnlynpm run buildtestjesttest:coveragejest --coveragetest:watchjest --watch
Dependencies10
@noalia/codetitan-core1.1.5axios^1.16.0chalk^4.1.2cli-progress^3.12.0cli-table3^0.6.3commander^12.0.0conf^10.2.0inquirer^8.2.6ora^5.4.1update-notifier5.1.0