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
- 17
- First published
- Feb 2026
- Publisher
- tallclub
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":["@matimo/[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":["@matimo/[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
Scripts10
buildtsc -p tsconfig.json && tsc -p tsconfig.tools.jsondevtsx src/index.tsformatprettier --write "src/**/*.ts" "test/**/*.ts" "*.json" "*.md"format:checkprettier --check "src/**/*.ts" "test/**/*.ts"linteslint src test --ext .tslint:fixeslint src test --ext .ts --fixtestjesttest:coveragejest --coveragetest:watchjest --watchwatchtsc --watch
Dependencies8
@modelcontextprotocol/sdk^1.29.0axios^1.15.2dotenv^17.2.3glob^10.5.0js-yaml^4.1.1winston^3.19.0yaml^2.8.2zod^4.3.6