Loading the registry…
Author, verify, and attest ERC-7730 Clear Signing descriptors
The publisher performed an authenticated act of publication — proving control of a namespace in the official MCP registry, or appearing in a first-party catalogue an operator curates. That establishes WHO published it. It is not a security finding, and attested artifacts carry Flagged verdicts too.
github: https://github.com/beepboop2025/lucent, 39 findings
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- lucent
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
13 findings · 11.1s
v0.3.26
6 findings · 5.4s
v0.1.0
0 findings · 6.1s
v0.1.0
0 findings · 6.1s
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.1s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image, nerlo-multi-source.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 11, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral: completenerlo-install-instruction: completecapslock ·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 19 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.
3 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-001, SECRET_PASSWORD_VAR · Files: tests/test_access.py, /repo/tests/test_payments.py, /repo/tests/test_verified_source.py · reported by agent-audit-kit, cisco-skill-scanner
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.
3 AAK-SECRET-004
Files: lucent/access.py, lucent/payments.py, scripts/watch.py · reported by agent-audit-kit
3 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/lucent/payments.py, /repo/lucent/verified_source.py, /repo/scripts/common.py · reported by cisco-skill-scanner
2 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md, /repo/dist/reviews/SKILL.md · reported by cisco-skill-scanner
2 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md, /repo/dist/reviews/SKILL.md · reported by cisco-skill-scanner
1 AAK-OAUTH-001
Files: lucent/access.py · reported by agent-audit-kit
1 AAK-SUPPLY-004
Files: pyproject.toml
High risk: credential exposure and resource abuse
The artifact handles credentials and may exhibit resource consumption issues. High severity findings indicate potential credential access via OAuth tokens and secrets in `lucent/access.py`, `lucent/payments.py`, and `scripts/watch.py`. Additionally, a high severity finding points to a potential infinite loop in `/repo/lucent/verified_source.py`, which could lead to resource exhaustion.
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.
1 RESOURCE_ABUSE_INFINITE_LOOP
Files: /repo/lucent/verified_source.py · reported by cisco-skill-scanner
1 TOOL_ABUSE_UNDECLARED_NETWORK
Files: /repo/repo/README.md · reported by cisco-skill-scanner