Production-grade visual agentic workflow portfolio.
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.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- aegisops-agentic-portfolio
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
0 findings · 0.9s
v2.0.11
73 findings · 15.2s
v0.3.74
14 findings · 11.4s
v0.1.0
1 finding · 6.9s
v0.1.0
1 finding · 6.9s
v0.71.0
36 findings · 0.5s
v2.3.8
44 findings · 11.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 · 2.0s
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 21, 2026 | Flagged32 | — | 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 169 findings across every scanner that examined this package.
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.
17 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, MANIFEST_INVALID_NAME · Files: /repo/.github/SKILL.md, /repo/docs/SKILL.md, /repo/docs/adrs/SKILL.md and 5 more · reported by cisco-skill-scanner
2 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-OAUTH-008 · Files: services/api/tests/test_http_json_adapters.py, services/api/tests/test_github_adapter.py · reported by agent-audit-kit
1 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: TOOL_ABUSE_UNDECLARED_NETWORK · Files: /repo/repo/AGENTS.md · reported by cisco-skill-scanner
1 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 · reported by agent-audit-kit
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.
22 DATA_EXFIL_JS_NETWORK
Files: /repo/apps/web/app/test-drive/probe/route.ts, /repo/apps/web/lib/agentic/mcp-tools.ts, /repo/apps/web/lib/api.ts · reported by cisco-skill-scanner
11 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/infra/SKILL.md, /repo/mcp/SKILL.md and 8 more · reported by cisco-skill-scanner
11 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/infra/SKILL.md, /repo/mcp/SKILL.md and 8 more · reported by cisco-skill-scanner
6 AAK-SECRET-004
Files: services/api-vercel/main.py, services/api/src/aegisops_api/tools/adapters/github.py, services/api/src/aegisops_api/tools/adapters/http_json.py · reported by agent-audit-kit
3 GHSA-mh99-v99m-4gvg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
3 GHSA-rgw5-rvv9-x895
Artifact contains secrets and high-severity vulnerabilities, enabling network egress.
The artifact contains hardcoded secrets in `services/api-vercel/main.py` and `services/api/src/aegisops_api/tools/adapters/http_json.py`, which are then used for network egress. Multiple high-severity vulnerabilities are present in dependencies listed in `pnpm-lock.yaml`, which could lead to various compromises. Additionally, parts of the artifact are unanalyzable, posing an unknown risk.
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/pnpm-lock.yaml · reported by osv-scanner
3 LOW_ANALYZABILITY
Files: /repo, /repo/apps/web, /repo/packages/shared-contracts · reported by cisco-skill-scanner
2 AAK-LEGAL-002
Files: packages/shared-contracts/package.json, apps/web/package.json · reported by agent-audit-kit
2 BINARY_FILE_DETECTED
Files: /repo/apps/web/lib/agentic/policies/public-demo.wasm · reported by cisco-skill-scanner
2 GHSA-55q2-fjhq-7xh7
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-5p4m-2wfm-xmqj
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 GHSA-f88m-g3jw-g9cj
Files: /repo/pnpm-lock.yaml, pnpm-lock.yaml · reported by osv-scanner, trivy
2 GHSA-frvp-7c67-39w9
Files: pnpm-lock.yaml, /repo/pnpm-lock.yaml · reported by trivy, osv-scanner
2 MANIFEST_INVALID_NAME
Files: /repo/configs/replays/incident_response_investigator/SKILL.md, /repo/configs/replays/engineering_issue_to_pr/SKILL.md · reported by cisco-skill-scanner
2 UNANALYZABLE_BINARY
Files: /repo/apps/web/lib/agentic/policies/public-demo.wasm · reported by cisco-skill-scanner
1 AAK-MCP-018
Files: apps/web/lib/agentic/mcp-tools.ts · reported by agent-audit-kit
1 AAK-MCP-LANGGRAPH-CHECKPOINT-CVE-2026-71433-001
Files: pnpm-lock.yaml · reported by agent-audit-kit
1 AAK-MCP-SSRF-001
Files: apps/web/lib/agentic/mcp-tools.ts · reported by agent-audit-kit
1 CVE-2026-13697
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-14257
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-14643
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-15157
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16221
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16728
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-16729
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-18446
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-50159
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-54272
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64641
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64642
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64643
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64644
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64645
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64646
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64647
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64648
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-64649
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-67213
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69152
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69153
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69192
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69198
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-69207
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71436
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71437
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71438
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71439
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71848
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71849
Files: pnpm-lock.yaml · reported by trivy
1 CVE-2026-71850
Files: pnpm-lock.yaml · reported by trivy
1 EXCESSIVE_FILE_COUNT
Files: /repo/. · reported by cisco-skill-scanner
1 GHSA-22jq-vg5j-6vgg
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2m8v-j782-fhvr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2v37-7h3g-55p8
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-2v8p-3f2j-5mp7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-3rrr-jr9j-h3q3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4633-3j49-mh5q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4c39-4ccg-62r3
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4cwx-7wf7-3272
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-4xrf-jv44-h6hh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-54fx-42gc-7vw4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-68g3-v927-f742
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6gpp-xcg3-4w24
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-6x64-9x62-f2gx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-724g-mxrg-4qvm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-79qm-7rj5-m7r9
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-7p8r-x3mc-p8w7
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-89xv-2m56-2m9x
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-8r6m-32jq-jx6q
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-8xcm-r25x-g524
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-955p-x3mx-jcvp
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-c4c3-pg64-4m4v
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-f23p-vx2j-j53r
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-jr45-8vmc-qm54
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-m8rv-5g2x-5cg5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-m99w-x7hq-7vfj
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-mwp4-54f8-5fhr
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-p9j2-gv94-2wf4
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-pm4m-ph32-ghv5
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-q8wf-6r8g-63ch
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-rhh3-jpg6-66xh
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v2hh-gcrm-f6hx
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 GHSA-v3r7-h72x-cjcm
Files: /repo/pnpm-lock.yaml · reported by osv-scanner
1 opt.nerlo-rules.nerlo-install-run-bundled-artifact
Files: /repo/README.md · reported by nerlo-install-instruction
1 opt.nerlo-rules.nerlo-py-secret-to-network-egress
Files: /repo/services/api-vercel/main.py · reported by nerlo-behavioral
1 TOOL_ABUSE_UNDECLARED_NETWORK
Files: /repo/services/api/repo/services/api/README.md · reported by cisco-skill-scanner
Showing 25 of 40; the rest are in the per-scanner reports above.