Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for security teams that want LLM help on real shell output or pentest notes without sending raw client details straight to a hosted model provider.
Who should use it
Who should skip it
Skip zeroc00I/DontFeedTheAI if you cannot isolate its execution environment or audit what data it touches before connecting anything sensitive.
About this signal
zeroc00I/DontFeedTheAI is tracked by RepoRadar as a proxy in the Security section. It was first seen on 2026-06-26 and last updated on 2026-06-26. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. The standout signals for zeroc00I/DontFeedTheAI are workflow potential (9.3) and open-source/build quality (8.4), while setup ease (6.4) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned zeroc00I/DontFeedTheAI a composite score of 8.2 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 66.0 and never affects the composite score or tier. The risk label of 'medium' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The audit dashboard exposes the surrogate-to-original mapping, so it belongs only on a tightly controlled review path such as the documented SSH tunnel flow; Redaction misses are possible on unusual secrets or domain-specific identifiers, so review the anonymized output before trusting it with client material; It is designed for security and pentest workflows, so operators still need explicit authorization and their own retention policy for any captured data.