Ai Doc Gen
AI-powered multi-agent system that automatically analyzes codebases and generates comprehensive documentation. Features GitLab integration, concurrent processing, and multiple LLM support for better code understanding and developer onboarding.
Is Ai Doc Gen safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Ai Doc Gen
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Ai Doc Gen scores 42.7/100 (Grade D), ranked #303 of 351 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.1/10; 40% of recent commits are signed; last pushed 2026-07-21. Every point is earned from checkable signals — never paid placement. How scoring works →
How Ai Doc Gen compares in Agent Skills
- #301 Nexu 42.8 +0.1
- #302 Verilog Generator 42.7 ±0
- #303 Ai Doc Gen 42.7 this agent
- #304 Auteur 42.7 ±0
- #305 Story To Handdrawn Video 42.6 −0.1
Bars show each HVTrust score; the tick marks Ai Doc Gen’s 42.7.
Where the 42.7 comes from
HVTrust dimensions vs the Agent Skills average
42.7 / 100 · 100.0% confidenceAi Doc Gen Agent Skills average (351 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
42.0 / 100Supply Chain Trust
Common questions about Ai Doc Gen
Does Ai Doc Gen publish package provenance?
Does Ai Doc Gen have an OpenSSF Scorecard?
Is Ai Doc Gen actively maintained?
What license does Ai Doc Gen use?
Are Ai Doc Gen's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- code
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Ai Doc Gen's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Ai Doc Gen?
For maintainers
HVTrust scores Ai Doc Gen from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/ai-doc-gen)
<a href="https://hvtracker.net/agents/ai-doc-gen"><img src="https://hvtracker.net/badge/ai-doc-gen.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON