Loading the registry…
Backlog MCP server confined to an explicit allow-list of projects. Fork of nulab/backlog-mcp-server.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
npm: @fyosimi/fv-backlog-mcp-server @ 0.2.0, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- @fyosimi/fv-backlog-mcp-server
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
8 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.8s
v2.0.11
15 findings · 11.7s
v0.3.74
22 findings · 3.5s
v0.1.0
3 findings · 4.4s
v0.1.0
0 findings · 4.4s
v0.1.0
0 findings · 8.6s
v0.71.0
6 findings · 0.2s
v2.3.8
15 findings · 6.8s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.71.0
No container image was published for this artifact. What each scanner covers
0 findings · 0.0s
vv1.6.0
No Go modules were found in this artifact. What each scanner covers
0 findings · 0.1s
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 20, 2026 | Flagged53 | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source: completetrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
Out of 61 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 26 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
Two keys had to turn. The model had to name a reason from a fixed list of six, and a deterministic check of ours — over which files this artifact actually installs — had to independently agree. Anything it could not corroborate is in “not reviewed” above, at full severity.
6 Test or fixture file — The match is in a test or fixture. Our own check confirmed the file is not part of what gets installed.
Rules: AAK-SSRF-002, AAK-MCP-ROUTING-DESYNC-001, AAK-MCP-018 · Files: src/oauthAccessTokenContext.test.ts, src/httpMcpServer.test.ts · reported by agent-audit-kit
5 CI or editor configuration — The match is in build, CI or editor configuration, confirmed by our own check to be outside the installed artifact.
Rules: AAK-GHA-IMMUTABLE-001 · Files: .github/workflows/ci.yml, .github/workflows/release.yml · reported by agent-audit-kit
2 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: FILE_MAGIC_MISMATCH · Files: /repo/docs/URLlist.md · reported by cisco-skill-scanner
The model could have called any of these a false positive and did not.
3 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/src/auth/backlogOAuthClient.ts · reported by nerlo-behavioral
2 AAK-MCP-018
Files: src/createBacklogMcpServer.ts, src/index.ts · reported by agent-audit-kit
2 GHSA-5p4m-2wfm-xmqj
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
1 AAK-MCP-HTTP-NOAUTH-SERVER-001
Files: src/httpMcpServer.ts · reported by agent-audit-kit
1 AAK-OAUTH-005
Files: src/auth/bearerAuthMiddleware.ts · reported by agent-audit-kit
1 AAK-SECRET-004
Files: src/utils/tokenCounter.ts · reported by agent-audit-kit
1
26 The model's answer could not be read.
Rules: CVE-2026-69207, FILE_MAGIC_MISMATCH, AAK-OAUTH-005 and 14 more · Files: pnpm-lock.yaml, /repo/src/tools/tools.ts, src/auth/backlogOAuthClient.test.ts and 11 more · reported by trivy, cisco-skill-scanner, agent-audit-kit and 1 more
High severity findings, including secrets to network egress.
The artifact contains code that sends secrets over the network, specifically identified in `src/auth/backlogOAuthClient.ts`. It also logs sensitive tokens in `src/auth/bearerAuthMiddleware.ts` and `src/utils/tokenCounter.ts`, and includes an unauthenticated HTTP server in `src/httpMcpServer.ts`. Additionally, several high-severity vulnerabilities are present in dependencies listed in `pnpm-lock.yaml`.
Concern level assessed by the review: High. This is the review's scale, not the registry badge.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.
Files: src/auth/bearerAuthMiddleware.ts · reported by agent-audit-kit
1 CVE-2026-59869
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71848
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71850
Files: pnpm-lock.yaml · reported by trivy
1 GHSA-2v37-7h3g-55p8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3jxr-9vmj-r5cp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8j4g-w8fx-2239
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rgw5-rvv9-x895
Files: /repo/pnpm-lock.yaml · reported by osv-scanner