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
- 1
- First published
- May 2026
- Publisher
- gadz82
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":["@orchid-ai/[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":["@orchid-ai/[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
buildtsupdevtsx watch src/index.tsformatprettier --write .format:checkprettier --check .linteslint .lint:fixeslint . --fixstartnode dist/index.jstestvitest runtest:coveragevitest run --coveragetest:watchvitesttypechecktsc --noEmit
Dependencies10
@modelcontextprotocol/sdk1.26.0@opentelemetry/api^1.9.0@opentelemetry/instrumentation-undici^0.6.0@opentelemetry/sdk-node^0.54.0lru-cache^11.0.2openid-client^6.1.7opossum^9.0.0pino^9.5.0undici^7.0.0zod^3.23.8
Optional dependencies1
ioredis^5.4.1