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
- 41
- First published
- Feb 2026
- Publisher
- goodgidanc
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":["@aiassesstech/[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":["@aiassesstech/[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
Scripts9
buildtsc && npm run copy-assetscopy-assetscp src/store/schema.sql dist/store/schema.sqldevtsc --watchlinttsc --noEmitprepublishOnlynpm run typecheck && npm run test && npm run buildtestvitest runtest:coveragevitest run --coveragetest:watchvitesttypechecktsc --noEmit
Dependencies7
@aiassesstech/fleet-alerting^0.1.2@aiassesstech/fleet-bus^0.5.0@aiassesstech/prompt-shield^0.1.0better-sqlite3^12.6.2chokidar^4.0.3cron-parser^5.5.0zod^3.22.0