Loading the registry…
Visual editor for AI agent flow configurations
Cursor Rules are .cursorrules / .cursor/rules files that steer Cursor's AI; 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.
Cursor Rules are .cursorrules / .cursor/rules files that steer Cursor's AI. Review the scanned source before copying them into your own project.
nerlo install -- ai-agent-flow-editor
5 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.5s
v2.0.11
41 findings · 7.3s
v0.3.74
4 findings · 2.4s
v0.1.0
4 findings · 3.6s
v0.1.0
0 findings · 3.6s
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.7s
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 22, 2026 | Scan Halted | — | agentshield: completecisco-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.
Out of 49 findings across every scanner that examined this package.
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.
28 DATA_EXFIL_JS_NETWORK
Files: /repo/app/api/job/list/route.ts, /repo/app/api/job/start/route.ts, /repo/app/api/job/stop/route.ts and 8 more · reported by cisco-skill-scanner
5 DATA_EXFIL_JS_FS_ACCESS
Files: /repo/app/api/workspace/load/[name]/[version]/route.ts, /repo/app/api/workspace/versions/[name]/route.ts, /repo/server.js and 2 more · reported by cisco-skill-scanner
4 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/app/api/job/list/route.ts, /repo/app/api/job/start/route.ts, /repo/app/api/job/stop/route.ts and 1 more · reported by nerlo-behavioral
2 AAK-SECRET-004
Files: middleware.ts, utils/auth.ts · reported by agent-audit-kit
2 FILE_MAGIC_MISMATCH
Files: /repo/components/constants.ts · reported by cisco-skill-scanner
2 LOW_ANALYZABILITY
Files: /repo, /repo/components · reported by cisco-skill-scanner
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/components/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/components/SKILL.md · reported by cisco-skill-scanner
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
Artifact has file system access, network egress with secrets, and hardcoded credentials.
The artifact exhibits capabilities for file system access in multiple API routes and `server.js`, which could lead to data exfiltration. It also performs network egress operations that involve secrets in several API routes, including `/repo/app/api/job/list/route.ts` and `/repo/app/api/team/call/route.ts`. Additionally, hardcoded secrets are present in `middleware.ts` and `utils/auth.ts`, posing a credential access risk. The presence of low analyzability findings in `/repo` and `/repo/components` further complicates security assessment.
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.