Loading the registry…
Add your description here
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.
1 critical finding reported by osv-scanner. The composite score alone does not reflect this — read the per-scanner reports below.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- mcp-repo-onboarding
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
6 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.
v2.0.11
80 findings · 11.4s
v0.3.74
9 findings · 4.3s
v0.1.0
0 findings · 2.8s
v0.1.0
1 finding · 2.8s
v0.71.0
32 findings · 0.3s
v2.3.8
53 findings · 1.4s
v1.4.0
None of the entry points this scanner reads were found in this artifact. What each scanner covers
0 findings · 0.2s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.8s
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
2 scans on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Sep 3, 2026 | Flagged35 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicabletrivy: completeosv-scanner: completetrivy_image ·n/a: not applicablegovulncheck ·n/a: not applicable | completed |
| Aug 11, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·n/a: not applicable | rejected |
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 175 findings across every scanner that examined this package. None of the 1 finding rated critical by their scanner were dismissed.
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.
46 Agent instruction file — The match is in a file that instructs an AI coding agent — a CLAUDE.md or similar. It is documentation of intent, and our own check confirmed it is not part of what gets installed.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/.github/SKILL.md, /repo/tests/fixtures/setuptools-only-no-install/SKILL.md, /repo/tests/fixtures/excessive-docs-configs/SKILL.md and 20 more · reported by cisco-skill-scanner
21 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: PYSEC-2018-28, HIDDEN_EXECUTABLE_SCRIPT, FILE_MAGIC_MISMATCH and 9 more · Files: /repo/tests/fixtures/fixture-exclusion-test/tests/fixtures/ignored_requirements.txt, /repo/tests/fixtures/ignore_handling/repo_safety_override/.venv/fake.py, /repo/tests/fixtures/ignore_handling/repo_no_gitignore/.venv/lib.py and 11 more · reported by osv-scanner, cisco-skill-scanner
7 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: opt.nerlo-rules.nerlo-install-pipe-to-shell, FILE_MAGIC_MISMATCH, MANIFEST_INVALID_NAME · Files: /repo/docs/legacy/testing_results_ab/DeepCode/A.md, /repo/tests/fixtures/excessive-docs-configs/docs/admin/install.md, /repo/docs/legacy/testing_results_ab/Paper2Code/SKILL.md and 1 more · reported by nerlo-install-instruction, cisco-skill-scanner
4 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, MANIFEST_INVALID_NAME · Files: .github/workflows/ci.yml, /repo/.github/SKILL.md, /repo/.github/ISSUE_TEMPLATE/SKILL.md · reported by agent-audit-kit, cisco-skill-scanner
These findings are in files this artifact installs and are not placeholder values. No false-positive basis can be corroborated for such a finding, so this review never dismisses one; they were not sent to the model and stand at their scanner's severity.
3 HIDDEN_DATA_FILE
Files: /repo/.pre-commit-config.yaml, /repo/.gemini/settings.json, /repo/.gemini/B-prompt.txt · reported by cisco-skill-scanner
3 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/notes/SKILL.md, /repo/src/mcp_repo_onboarding/SKILL.md · reported by cisco-skill-scanner
3 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/notes/SKILL.md, /repo/src/mcp_repo_onboarding/SKILL.md · reported by cisco-skill-scanner
2 AAK-MCP-SDK-CVE-2026-52869-001
Files: pyproject.toml, uv.lock · reported by agent-audit-kit
2 GHSA-4xgf-cpjx-pc3j
Files: /repo/uv.lock, uv.lock · reported by osv-scanner, trivy
2 GHSA-537c-gmf6-5ccf
The model could have called any of these a false positive and did not.
1 CVE-2026-54282
Files: uv.lock · reported by trivy
1 CVE-2026-69248
Files: uv.lock · reported by trivy
Critical vulnerability and multiple high-severity issues detected.
This artifact contains a critical vulnerability (PYSEC-2026-36) in its dependencies, which could lead to severe system compromise. Additionally, a hardcoded secret (AAK-SECRET-004) is present in `src/mcp_repo_onboarding/analysis/frameworks.py`, potentially allowing unauthorized credential access. Numerous other high-severity vulnerabilities are identified across various dependencies, including several related to CVE-2026-52869 and other PYSEC issues, which may enable further system impact.
Concern level assessed by the review: Critical. 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.
1 AAK-AGENT-TRUST-004
Files: GEMINI.md · reported by agent-audit-kit
1 AAK-MCP-006
Files: .gemini/settings.json · reported by agent-audit-kit
1 AAK-MCP-ATTEST-001
Files: .gemini/settings.json · reported by agent-audit-kit
1 AAK-SEC-MD-001
Files: SECURITY.md · reported by agent-audit-kit
1 AAK-SECRET-004
Files: src/mcp_repo_onboarding/analysis/frameworks.py · reported by agent-audit-kit
1 CVE-2026-24486
Files: uv.lock · reported by trivy
1 CVE-2026-26007
Files: uv.lock · reported by trivy
1 CVE-2026-28684
Files: uv.lock · reported by trivy
1 CVE-2026-32597
Files: uv.lock · reported by trivy
1 CVE-2026-34073
Files: uv.lock · reported by trivy
1 CVE-2026-39892
Files: uv.lock · reported by trivy
1 CVE-2026-40347
Files: uv.lock · reported by trivy
1 CVE-2026-42561
Files: uv.lock · reported by trivy
1 CVE-2026-4539
Files: uv.lock · reported by trivy
1 CVE-2026-45409
Files: uv.lock · reported by trivy
1 CVE-2026-48522
Files: uv.lock · reported by trivy
1 CVE-2026-48523
Files: uv.lock · reported by trivy
1 CVE-2026-48524
Files: uv.lock · reported by trivy
1 CVE-2026-48525
Files: uv.lock · reported by trivy
1 CVE-2026-48526
Files: uv.lock · reported by trivy
1 CVE-2026-48710
Files: uv.lock · reported by trivy
1 CVE-2026-48817
Files: uv.lock · reported by trivy
1 CVE-2026-48818
Files: uv.lock · reported by trivy
1 CVE-2026-52869
Files: uv.lock · reported by trivy
1 CVE-2026-52870
Files: uv.lock · reported by trivy
1 CVE-2026-53537
Files: uv.lock · reported by trivy
1 CVE-2026-53538
Files: uv.lock · reported by trivy
1 CVE-2026-53539
Files: uv.lock · reported by trivy
1 CVE-2026-53540
Files: uv.lock · reported by trivy
1 CVE-2026-54283
Files: uv.lock · reported by trivy
1 CVE-2026-59950
Files: uv.lock · reported by trivy
1 CVE-2026-69247
Files: uv.lock · reported by trivy
1 CVE-2026-69249
Files: uv.lock · reported by trivy
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 MANIFEST_INVALID_NAME
Files: /repo/src/mcp_repo_onboarding/SKILL.md · reported by cisco-skill-scanner
1 PYSEC-2025-183
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-120
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1374
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-142
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-161
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-175
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-176
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-177
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-178
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-179
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1796
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1845
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1852
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-196
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-1996
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2009
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2132
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2141
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-215
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2270
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2275
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2280
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2281
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-248
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-249
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2875
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2876
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-2987
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3036
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3037
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3038
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3039
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3040
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3041
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3481
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3482
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3483
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-35
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3552
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3553
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3554
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-36
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3625
Files: /repo/uv.lock · reported by osv-scanner
1 PYSEC-2026-3721
Files: /repo/uv.lock · reported by osv-scanner
Showing 25 of 39; the rest are in the per-scanner reports above.