Item detail
github.com

yv1ing/Z3r0

RepoRadar surfaced yv1ing/Z3r0 — an agent project — into the Radar section, where it sits at Silver tier with a 'worth watch' verdict. Its strongest signal is open-source/build quality, scored 8.4 out of 10.

Score6.8
Popularity5.3
Riskmedium
TierSilver
Score breakdown
Usefulness7.0
Novelty7.5
Momentum6.0
Maturity5.1
Open-source/build8.4
Evidence7.2
Workflow potential7.6
Setup ease4.2

Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.

Why it matters

Useful for security teams, bug-bounty hunters, and red-team consultants who want a single operator console for running multi-step authorized pentests with a durable evidence plane instead of stitching ad-hoc shell sessions and findings together by hand.

Who should use it

security teams running authorized penetration tests bug-bounty hunters who want a durable evidence plane red-team consultants building replayable assessment timelines developers integrating MCP-backed agents into a security workflow educators building a structured red-team curriculum

Who should skip it

Hold off on yv1ing/Z3r0 for mission-critical workflows without a containment strategy, explicit approvals, and a hands-on security review.

About this signal

yv1ing/Z3r0 is tracked by RepoRadar as an agent project in the Radar section. First seen 2026-07-12; the source record was last checked on 2026-07-12. The current verdict is 'worth watch' with a Silver tier and advanced setup difficulty. Across RepoRadar's eight signals, yv1ing/Z3r0 is strongest on open-source/build quality (8.4) and workflow potential (7.6) and weakest on setup ease (4.2) — a profile worth weighing against your own priorities. This page summarizes the public evidence on the linked source page and states where additional review is still needed.

How this item is evaluated

The yv1ing/Z3r0 record combines a 6.8/10 composite score with separate popularity (5.3), risk (medium), and setup (advanced) signals. See the scoring methodology for the current weights and evidence definitions.

Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.

Risk explanation

It is a security workbench — deployment in regulated or multi-tenant environments requires the same human-in-the-loop controls as any offensive-security tooling; The default sandbox image bundles credential-testing and reverse-engineering tools that may require additional policy review before use.

Evidence links
Closest alternatives / related signals
security penetration-testing red-team agent-framework mcp self-hosted docker fastapi
Verification record

What RepoRadar actually verified

Discovered

Automated discovery and source capture. Last checked 2026-08-13T20:20:15Z.

No editorial or hands-on review is claimed. This record remains at Discovered.

Verification sources

Longitudinal intelligence

How this decision record is moving

Raw history JSON →

25 dated snapshots retained from 2026-07-12 through 2026-08-13; see the snapshot index for explicit coverage gaps. Stars, version, release, pricing, integration, risk, maintenance, verdict, score, and momentum fields remain explicit even when a source has not reported them. Repository momentum is a normalized 0–10 RepoRadar signal; GitHub stars appear only where the popularity monitor retained exact timestamped observations.

RepoRadar score6.8 current · +0.0 net
Repository momentum9.0 current · +3.0 net
GitHub stars (observed)615 current · +83 net
GitHub stars615 exact observation
Versionv0.2.2
Last release2026-07-21T03:24:29Z
Maintenanceactive
Current riskmedium
Current verdictworth watch
Pricing baselineNo structured commercial pricing baseline
Pricing checkedNot applicable or not recorded
Pricing freshnessNo dated commercial pricing review
Integrations baselineNo structured integrations recorded

Recent dated points

DateScoreMomentumStarsRiskVerdictMaintenance
2026-08-136.89.0615mediumworth watchactive
2026-08-126.89.0614mediumworth watchactive
2026-08-116.87.8613mediumworth watchactive
2026-08-106.87.5612mediumworth watchactive
2026-08-096.87.5612mediumworth watchactive
2026-08-086.87.8611mediumworth watchactive
2026-08-076.89.3600mediumworth watchactive
2026-08-066.86.0Not recordedmediumworth watchnot recorded
2026-08-056.86.0Not recordedmediumworth watchnot recorded
2026-08-046.89.3600mediumworth watchactive
2026-08-036.89.3600mediumworth watchactive
2026-08-026.89.3598mediumworth watchactive

Why the record changed

stars changed

Stars changed: 614 → 615.

stars changed

Stars changed: 613 → 614.

stars changed

Stars changed: 612 → 613.

stars changed

Stars changed: 611 → 612.

stars changed

Stars changed: 600 → 611.

stars changed

Stars changed: 598 → 600.

stars changed

Stars changed: 595 → 598.

stars changed

Source-observed stars changed: 594 → 595. This reports the retained observation delta and does not infer why the upstream change occurred.

stars changed

Stars changed: 577 → 580.

stars changed

Source-observed stars changed: 576 → 577. This reports the retained observation delta and does not infer why the upstream change occurred.

version changed

Version changed: v0.2.1 → v0.2.2.

stars changed

Stars changed: 544 → 576.