Loading the registry…
Prismatic Pay project with separate frontend and backend workspaces.
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 -- prismatic-pay
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- prismatic-pay ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
7 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
2 findings · 1.4s
v2.0.11
34 findings · 9.0s
v0.3.74
2 findings · 2.6s
v0.1.0
0 findings · 3.9s
v0.1.0
0 findings · 3.9s
v0.71.0
30 findings · 0.3s
v2.3.8
41 findings · 9.7s
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.9s
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 22, 2026 | Flagged40 | — | agentshield: completecisco-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 |
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 109 findings across every scanner that examined this package.
Not reviewed is not the same as clean. Those 2 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.
8 Documentation or example — The match is in documentation or sample code, confirmed by our own check to be outside the installed artifact.
Rules: SOCIAL_ENG_VAGUE_DESCRIPTION, MANIFEST_MISSING_LICENSE · Files: /repo/docs/SKILL.md, /repo/docs/decisions/SKILL.md, /repo/docs/design/SKILL.md and 1 more · reported by 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.
9 MANIFEST_MISSING_LICENSE
Files: /repo/.claude/skills/code-review/SKILL.md, /repo/.claude/skills/ui-sync/SKILL.md, /repo/.claude/skills/release/SKILL.md and 6 more · reported by cisco-skill-scanner
9 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/.claude/skills/code-review/SKILL.md, /repo/.claude/skills/ui-sync/SKILL.md, /repo/.claude/skills/release/SKILL.md and 6 more · reported by cisco-skill-scanner
4 LOW_ANALYZABILITY
Files: /repo/backend/api, /repo/frontend, /repo/backend and 1 more · reported by cisco-skill-scanner
2 FILE_MAGIC_MISMATCH
Files: /repo/backend/app.ts · reported by cisco-skill-scanner
2 GHSA-3jxr-9vmj-r5cp
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-42h9-826w-cgv3
2 The model called these false positives and our own check did not agree, so the dismissal was refused.
Rules: HIDDEN_DATA_FILE · Files: /repo/frontend/.env.local.example · reported by cisco-skill-scanner
High severity vulnerabilities in dependencies and low code analyzability
The artifact includes dependencies with multiple high severity vulnerabilities, as identified in `package-lock.json`. Additionally, significant portions of the installed code, specifically within `/repo`, `/repo/backend`, `/repo/backend/api`, and `/repo/frontend`, exhibit low analyzability. This low analyzability could obscure further risks or make it difficult to assess the full impact of the identified vulnerabilities.
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: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-7q8q-rj6j-mhjq
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-f4gw-2p7v-4548
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-f88m-g3jw-g9cj
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-gcfj-64vw-6mp9
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-hcpx-6fm6-wx23
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-jqh4-m9w3-8hp9
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-mh99-v99m-4gvg
Files: /repo/package-lock.json · reported by osv-scanner
2 GHSA-mmx7-hfxf-jppx
Files: package-lock.json, /repo/package-lock.json · reported by trivy, osv-scanner
2 GHSA-mwf2-3pr3-8698
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-pmv8-rq9r-6j72
Files: /repo/package-lock.json, package-lock.json · reported by osv-scanner, trivy
2 GHSA-rgw5-rvv9-x895
Files: /repo/package-lock.json · reported by osv-scanner
2 hooks-no-pretooluse
Files: settings.json, .claude/settings.json · reported by agentshield
1 AAK-LEGAL-002
Files: package.json · reported by agent-audit-kit
1 AAK-SUPPLY-005
Files: package-lock.json · reported by agent-audit-kit
1 CVE-2026-12143
Files: package-lock.json · reported by trivy
1 CVE-2026-12590
Files: package-lock.json · reported by trivy
1 CVE-2026-5078
Files: package-lock.json · reported by trivy
1 CVE-2026-54272
Files: package-lock.json · reported by trivy
1 CVE-2026-64641
Files: package-lock.json · reported by trivy
1 CVE-2026-64642
Files: package-lock.json · reported by trivy
1 CVE-2026-64643
Files: package-lock.json · reported by trivy
1 CVE-2026-64644
Files: package-lock.json · reported by trivy
1 CVE-2026-64645
Files: package-lock.json · reported by trivy
1 CVE-2026-64646
Files: package-lock.json · reported by trivy
1 CVE-2026-64647
Files: package-lock.json · reported by trivy
1 CVE-2026-64648
Files: package-lock.json · reported by trivy
1 CVE-2026-64649
Files: package-lock.json · reported by trivy
1 CVE-2026-67213
Files: package-lock.json · reported by trivy
1 CVE-2026-67214
Files: package-lock.json · reported by trivy
1 CVE-2026-67314
Files: package-lock.json · reported by trivy
1 CVE-2026-69153
Files: package-lock.json · reported by trivy
1 CVE-2026-69192
Files: package-lock.json · reported by trivy
1 CVE-2026-69198
Files: package-lock.json · reported by trivy
1 CVE-2026-73646
Files: package-lock.json · reported by trivy
1 GHSA-22jq-vg5j-6vgg
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-28wg-ghj8-5hjv
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4633-3j49-mh5q
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4c39-4ccg-62r3
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4vj7-5mj6-jm8m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4x5r-pxfx-6jf8
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-4xrf-jv44-h6hh
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-52cp-r559-cp3m
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-5p4m-2wfm-xmqj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-68g3-v927-f742
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-6gpp-xcg3-4w24
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-89xv-2m56-2m9x
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-955p-x3mx-jcvp
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-fxqj-rqcc-2cmp
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-h67p-54hq-rp68
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-hmw2-7cc7-3qxx
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-m99w-x7hq-7vfj
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-mwp4-54f8-5fhr
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-p9j2-gv94-2wf4
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-q8wf-6r8g-63ch
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-r28c-9q8g-f849
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-v422-hmwv-36x6
Files: /repo/package-lock.json · reported by osv-scanner
1 GHSA-xj6q-8x83-jv6g
Files: /repo/package-lock.json · reported by osv-scanner
Showing 25 of 34; the rest are in the per-scanner reports above.