Loading the registry…
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.
Choose your runtime: the CLI writes the mcpServers config entry for that target.
nerlo install --target claude-code -- ugo2000/random-monetize
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
17 findings · 6.4s
v0.3.74
4 findings · 1.2s
v0.1.0
5 findings · 3.2s
v0.1.0
0 findings · 3.2s
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
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 0.9s
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 21, 2026 | Scan Halted | — | agentshield ·n/a: not applicablecisco-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 26 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.
12 DATA_EXFIL_NETWORK_REQUESTS
Files: /repo/buyer.py, /repo/buyer_agent.py, /repo/deploy_m2m.py and 1 more · reported by cisco-skill-scanner
5 opt.nerlo-rules.nerlo-py-secret-to-network-egress
Files: /repo/buyer.py, /repo/buyer_agent.py, /repo/payout_crypto.py and 1 more · reported by nerlo-behavioral
2 AAK-SECRET-004
Files: seller.py · reported by agent-audit-kit
2 RESOURCE_ABUSE_INFINITE_LOOP
Files: /repo/buyer.py, /repo/buyer_agent.py · reported by cisco-skill-scanner
1 AAK-MCP-NOAUTH-DEFAULT
Files: seller.py · reported by agent-audit-kit
1 AAK-OAUTH-008
Files: seller.py · reported by agent-audit-kit
1 MANIFEST_MISSING_LICENSE
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 SOCIAL_ENG_VAGUE_DESCRIPTION
Files: /repo/SKILL.md · reported by cisco-skill-scanner
1 TOOL_ABUSE_UNDECLARED_NETWORK
Files: /repo/repo/README.md · reported by cisco-skill-scanner
High risk of secret exposure via network egress and resource abuse.
The artifact performs network egress of secrets from `buyer.py`, `buyer_agent.py`, `payout_crypto.py`, and `seller.py`. Potential infinite loops in `buyer.py` and `buyer_agent.py` could lead to resource abuse. A default no-authentication configuration is present in `seller.py`, alongside other secrets. Undeclared network activity is also observed.
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.