Loading the registry…
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.
4 critical findings reported by trivy. The composite score alone does not reflect this — read the per-scanner reports below.
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 -- efrnds/opinioteca
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.
v2.0.11
402 findings · 12.1s
v0.3.74
5 findings · 7.2s
v0.1.0
72 findings · 9.0s
v0.1.0
0 findings · 9.0s
vv0.3.2
Incomplete run
0 findings · 0.4s
v0.71.0
82 findings · 0.5s
v2.3.8
38 findings · 0.7s
v1.4.0
None of the entry points this scanner reads 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 · 0.8s
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 | Flagged39 | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·!: incompletenerlo-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 599 findings across every scanner that examined this package. None of the 4 findings rated critical by their scanner were dismissed.
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.
2 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: AAK-AGENT-005 · Files: CLAUDE.md · reported by agent-audit-kit
2 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 · 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.
388 DATA_EXFIL_JS_NETWORK
Files: /repo/frontend/app/admin/assinaturas/page.tsx, /repo/frontend/app/admin/categorias/page.tsx, /repo/frontend/app/admin/denuncias/page.tsx and 107 more · reported by cisco-skill-scanner
72 opt.nerlo-rules.nerlo-js-secret-to-network-egress
Files: /repo/frontend/app/api/auth/validate-identity/route.ts, /repo/frontend/app/api/avaliacoes/[id]/comentarios/route.ts, /repo/frontend/app/api/avaliacoes/[id]/route.ts and 57 more · reported by nerlo-behavioral
4 HIDDEN_DATA_FILE
Files: /repo/.pnpm-store/v11/index.db, /repo/.repomixignore, /repo/.rtk.toml and 1 more · reported by cisco-skill-scanner
2 CVE-2026-41305
Files: frontend/pnpm-lock.yaml · reported by trivy
2 CVE-2026-45623
Files: frontend/pnpm-lock.yaml · reported by trivy
2 CVE-2026-69153
Files: frontend/pnpm-lock.yaml · reported by trivy
2 CVE-2026-73418
Files: frontend/pnpm-lock.yaml · reported by trivy
2 CVE-2026-73419
Files: frontend/pnpm-lock.yaml · reported by trivy
2 CVE-2026-73420
Files: frontend/pnpm-lock.yaml · reported by trivy
2 CVE-2026-73646
Files: frontend/pnpm-lock.yaml · reported by trivy
2 EXCESSIVE_FILE_COUNT
Files: /repo/., /repo/frontend/. · reported by cisco-skill-scanner
2 GO-2026-5932
Files: backend/go.mod, /repo/backend/go.mod · reported by trivy, osv-scanner
2 LOW_ANALYZABILITY
Files: /repo/frontend, /repo · reported by cisco-skill-scanner
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/frontend/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/frontend/SKILL.md · reported by cisco-skill-scanner
1 AAK-LEGAL-002
Files: frontend/package.json · reported by agent-audit-kit
1 AAK-OAUTH-001
Files: frontend/auth.ts · reported by agent-audit-kit
1 AAK-OAUTH-007
Files: frontend/auth.ts · reported by agent-audit-kit
1 CVE-2020-26160
Files: backend/go.mod · reported by trivy
1 CVE-2025-55182
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2025-59471
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2025-59472
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-13149
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-13676
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-13697
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-14257
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-14643
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-15157
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-16221
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-16728
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-16729
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-18446
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-27977
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-27978
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-27979
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-27980
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-29057
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44572
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44573
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44574
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44575
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44576
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44577
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44578
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44579
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44580
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44581
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-44582
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-45109
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-45149
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-46603
Files: backend/go.mod · reported by trivy
1 CVE-2026-49356
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-53550
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-54272
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-59869
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-59895
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-59896
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-59897
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-64641
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-64642
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-64643
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-64644
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-64645
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-64646
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-64647
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-64648
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-64649
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-67213
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-67214
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-69152
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-69192
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-69198
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-69207
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-71848
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-71849
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-71850
Files: frontend/pnpm-lock.yaml · reported by trivy
1 CVE-2026-73421
Files: frontend/pnpm-lock.yaml · reported by trivy
1 GHSA-5p4m-2wfm-xmqj
Files: frontend/pnpm-lock.yaml · reported by trivy
1 GHSA-8h8q-6873-q5fj
Files: frontend/pnpm-lock.yaml · reported by trivy
1 GHSA-f88m-g3jw-g9cj
Files: frontend/pnpm-lock.yaml · reported by trivy
1 GHSA-frvp-7c67-39w9
Files: frontend/pnpm-lock.yaml · reported by trivy
1 GHSA-h25m-26qc-wcjf
Files: frontend/pnpm-lock.yaml · reported by trivy
1 GHSA-mwv6-3258-q52c
Files: frontend/pnpm-lock.yaml · reported by trivy
1 GHSA-q4gf-8mx6-v5v3
Files: frontend/pnpm-lock.yaml · reported by trivy
1 GHSA-w37m-7fhw-fmv9
Files: frontend/pnpm-lock.yaml · reported by trivy
1 GO-2020-0017
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2025-4155
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2025-4175
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4337
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4340
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4341
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4342
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4601
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4602
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4603
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4864
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4865
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4869
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4870
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4918
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4946
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4947
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4970
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4971
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4976
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4977
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4980
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4981
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4982
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-4986
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-5026
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-5037
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-5038
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-5039
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-5856
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-5972
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-6088
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-6089
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-6090
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-6091
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-6218
Files: /repo/backend/go.mod · reported by osv-scanner
1 GO-2026-6222
Files: /repo/backend/go.mod · reported by osv-scanner
Critical vulnerabilities and potential credential exposure with network egress.
The artifact contains critical vulnerabilities in dependencies listed in `frontend/pnpm-lock.yaml`. Multiple frontend API routes are identified with potential credential exposure and network egress capabilities. Specifically, `frontend/auth.ts` shows potential OAuth credential access, and numerous frontend API routes exhibit network egress behavior.
Concern level assessed by the review: Critical. This is the review's scale, not the registry badge.
Showing 25 of 114; the rest are in the per-scanner reports above.
Reviewed by gemini-2.5-flash. The model sees the findings, not your code, and cannot change a score.