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
- 8
- First published
- Oct 2025
- Publisher
- rkeene-keeta
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":["@keetanetwork/[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":["@keetanetwork/[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
eslinteslintmake:allmake allmake:cleanmake cleanmake:distmake distmake:distcleanmake distcleanmake:do-lintmake do-lintmake:do-npm-packmake do-npm-packmake:testmake testpreparetsctsctscvitestvitest
Dependencies9
@google-cloud/cloudbuild5.3.1@google-cloud/run3.1.0@google-cloud/secret-manager6.1.1@pulumi/command1.1.3@pulumi/gcp9.6.0@pulumi/pulumi3.122.0@pulumi/random4.18.4@pulumi/tls5.2.3google-auth-library10.5.0