Loading the registry…
Define LLM-powered backend actions as Markdown. Generate typed clients. Run them anywhere.
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.
npm: mdlang @ 1.0.1, 0 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- mdlang
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.9s
v2.0.11
19 findings · 9.6s
v0.3.74
2 findings · 2.7s
v0.1.0
0 findings · 5.2s
v0.1.0
0 findings · 5.2s
v0.1.0
0 findings · 10.2s
v0.71.0
6 findings · 0.2s
v2.3.8
13 findings · 8.3s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.2s
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 | Flagged61 | — | 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 40 findings across every scanner that examined this package. None of the 1 finding rated critical by their scanner were dismissed.
Not reviewed is not the same as clean. Those 9 findings stand exactly as their scanners reported them, at full severity, as they would have without this review.
The model could have called any of these a false positive and did not.
9 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/src/cli/dataset.ts, /repo/src/cli/generate.ts, /repo/src/cli/import-style.ts and 2 more · reported by cisco-skill-scanner
2 GHSA-5p4m-2wfm-xmqj
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 LOW_ANALYZABILITY
Files: /repo, /repo/templates · reported by cisco-skill-scanner
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2026-18446
Files: package-lock.json · reported by trivy
1 CVE-2026-69207
Files: package-lock.json · reported by trivy
1 CVE-2026-71848
Files: package-lock.json · reported by trivy
1 CVE-2026-71849
Files: package-lock.json · reported by trivy
1 CVE-2026-71850
Files: package-lock.json · reported by trivy
1 GHSA-2v37-7h3g-55p8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4w7w-66w2-5vf9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-54fx-42gc-7vw4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5xrq-8626-4rwp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-67mh-4wv8-2f99
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-79qm-7rj5-m7r9
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-7p8r-x3mc-p8w7
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-8j4g-w8fx-2239
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-f23p-vx2j-j53r
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fx2h-pf6j-xcff
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-g7r4-m6w7-qqqr
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v6wh-96g9-6wx3
Files: /repo/package-lock.json · reported by osv-scanner
9 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: FILE_MAGIC_MISMATCH, AAK-SEC-MD-001, MANIFEST_MISSING_LICENSE and 1 more · Files: /repo/templates/actions/example.md, SECURITY.md, /repo/SKILL.md and 2 more · reported by cisco-skill-scanner, agent-audit-kit
Critical vulnerability and high-risk operations identified.
A critical vulnerability (GHSA-5xrq-8626-4rwp) is present in `package-lock.json`. Multiple high-severity findings from the bearer scanner indicate potential for sensitive data exposure or insecure operations within CLI files such as `src/cli/dataset.ts`, `src/cli/generate.ts`, and `src/cli/init.ts`. Other high-severity vulnerabilities are also noted in `package-lock.json`.
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.