Loading the registry…
Reviews the argument in an existing jPipe justification model (.jd). Takes exactly one .jd file as its scope, plus everything it transitively loads, since an argument spread over several files is still one argument; pass -m <model> to narrow that to one model in the file plus the models it is built from. Checks abstraction (each element at its right level), atomicity (one element, one job), grounding (the artifacts the evidence names exist in the repository), and the house style. Emits a findings report written for the engineer who built the system, then a fix list; nothing is edited until you approve it. Syntax errors are left to `jpipe diagnostic`. Use when asked to review, audit, critique or improve a .jd file or an assurance case; pass --global for every .jd in the repository instead. NOT for cross-model reuse, shared evidence or corpus consolidation, which is jpipe-survey's job; NOT for writing a model from scratch; NOT for reviewing the jpipe-runner step library or the jPipe compiler's own source.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
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.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'jpipe-mcscert/jpipe-skills (jpipe-review)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'jpipe-mcscert/jpipe-skills (jpipe-review)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 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
12 findings · 9.9s
v0.3.74
1 finding · 1.5s
v0.1.0
0 findings · 4.3s
v0.1.0
0 findings · 4.3s
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.2s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.3s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 18, 2026 | Scan Halted | — | 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 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.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 13 findings above stand exactly as their scanners reported them, at full severity.