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
- oaslananka
Recommended action
Review before promotingMixed signals: the package has indicators worth reading before allowing the update in automated dependency flows.
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
Credential file access: matched ".azure"
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 review · score 5 · status changed
Evidence
Static findings
1 static · 0 from release diff · showing high-signal first.
No high-signal findings — see all findings below.
Show all 1 findings (low-signal and informational)
| Severity | Kind | Path | Detail | Points |
|---|---|---|---|---|
| low | Credential file access | package/dist/azure-devops.js | matched ".azure" | 5 |
Manifest
Package metadata
Scripts29
buildnode -e "require('node:fs').rmSync('dist',{ recursive: true, force: true })" && tsc -p tsconfig.build.jsonbuild:cleanpnpm run buildcheck:metadatanode scripts/validate-mcp-metadata.mjscheck:packagepnpm pack --dry-runcipnpm run ci:check && pnpm run security && pnpm run security:supply-chain && pnpm run check:metadata && pnpm run check:package && pnpm run release:dry-runci:checkpnpm run build && pnpm run typecheck && pnpm run lint && pnpm run lint:test && pnpm run format:check && pnpm run docs:api:check && pnpm run test:coveragedevnode --loader ts-node/esm src/mcp.tsdocs:apitypedocdocs:api:checkpnpm run docs:api && node scripts/check-clean-path.mjs docs/apiformatprettier --write "src/**/*.ts" "test/**/*.ts"format:checkprettier --check "src/**/*.ts" "test/**/*.ts"linteslint "src/**/*.ts"lint:fixeslint --fix "src/**/*.ts" "test/**/*.ts"lint:testeslint "test/**/*.ts"preparepnpm run buildprepublishOnlynode scripts/prepublish-check.mjsrelease:dry-runnode scripts/release-state.mjs --dry-runsecuritypnpm audit --audit-level moderatesecurity:licensesnode scripts/check-license-policy.mjssecurity:reusepython -m reuse lintsecurity:sbomnode scripts/generate-sbom.mjssecurity:supply-chainpnpm run security:sbom && pnpm run security:licenses && pnpm run security:reusestartnode dist/mcp.jsstart:httpnode dist/server-http.jstestnode --experimental-vm-modules node_modules/jest/bin/jest.js --testPathPattern=test[/\\]unit[/\\]test:coveragenode --experimental-vm-modules node_modules/jest/bin/jest.js --coveragetest:integrationnode --experimental-vm-modules node_modules/jest/bin/jest.js --testPathPattern=test[/\\]integration[/\\]test:watchnode --experimental-vm-modules node_modules/jest/bin/jest.js --watchtypechecktsc -p tsconfig.json --noEmit
Dependencies3
@modelcontextprotocol/sdk1.27.1better-sqlite312.8.0zod3.25.76