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
- 3
- First published
- Mar 2024
- Publisher
- otakustay
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":["@comate/[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":["@comate/[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
Scripts 3
Sign in to view install / lifecycle script contents.
Dependencies15
@comate/plugin-engine^0.9.1@comate/plugin-playground^0.9.1@comate/plugin-shared-internals^0.9.1@rollup/plugin-commonjs^25.0.7@rollup/plugin-esm-shim^0.1.5@rollup/plugin-json^6.1.0@rollup/plugin-node-resolve^15.2.3@rollup/plugin-swc^0.3.0chokidar^3.5.3clear^0.1.0clipanion^3.2.1express^4.18.2kolorist^1.8.0p-queue^8.0.1rollup^4.9.5