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
- 611
- Versions published
- 9
- First published
- Jun 2026
- Publisher
- vashigor
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":["@owlmeans/[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":["@owlmeans/[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
Scripts4
buildtsc -bdevsleep 378 && nodemon -e ts,tsx,json --watch src --exec "tsc -p ./tsconfig.json"testbun test ./testswatchtsc -b -w --preserveWatchOutput --pretty
Dependencies14
@owlmeans/auth^0.1.11@owlmeans/basic-envelope^0.1.11@owlmeans/client^0.1.11@owlmeans/client-auth^0.1.11@owlmeans/client-flow^0.1.11@owlmeans/client-i18n^0.1.11@owlmeans/context^0.1.11@owlmeans/entrypoint^0.1.11@owlmeans/flow^0.1.11@owlmeans/oidc^0.1.11@owlmeans/resource^0.1.11@owlmeans/web-client^0.1.11@owlmeans/web-flow^0.1.11oidc-client-ts3.5.0