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
- 116
- Versions published
- 8
- First published
- Apr 2026
- Publisher
- automations-project
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":["[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":["[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
buildtsup --no-dts && tsc --allowJs --emitDeclarationOnly && node scripts/post-build-shebang.mjstestcd ../.. && npx vitest run packages/mcp-server/testtest:coveragecd ../.. && npx vitest run --coverage packages/mcp-server/testtypechecktsc -p tsconfig.json --noEmit
Dependencies8
@modelcontextprotocol/sdk^1.29.0@ngrok/ngrok^1.7.0express^5.2.1got-scraping^4.2.1gray-matter^4.0.3helmet^8.1.0patchright^1.59.4zod^3.24.0
Optional dependencies1
keytar^7.9.0