Plannotator
Annotate and review coding agent plans and code diffs visually, share with your team, send feedback to agents with one click.
Is Plannotator safe? Promising trust profile, but some evidence still deserves review.
Compare Plannotator
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Plannotator scores 66.7/100 (Grade B), ranked #49 of 351 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 7.0/10; 93% of recent commits are signed; last pushed 2026-09-25. Every point is earned from checkable signals — never paid placement. How scoring works →
How Plannotator compares in Agent Skills
- #47 SkillOpt 66.8 +0.1
- #48 Trailofbits Skills 66.7 ±0
- #49 Plannotator 66.7 this agent
- #50 Lobehub 66.7 ±0
- #51 Comet 66.4 −0.3
Bars show each HVTrust score; the tick marks Plannotator’s 66.7.
Where the 66.7 comes from
HVTrust dimensions vs the Agent Skills average
66.7 / 100 · 100.0% confidencePlannotator 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 B reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
86.9 / 100Supply Chain Trust
Common questions about Plannotator
Does Plannotator publish package provenance?
Does Plannotator have an OpenSSF Scorecard?
Is Plannotator actively maintained?
What license does Plannotator use?
Are Plannotator'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 →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Plannotator'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 Plannotator?
For maintainers
HVTrust scores Plannotator 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/plannotator)
<a href="https://hvtracker.net/agents/plannotator"><img src="https://hvtracker.net/badge/plannotator.svg" alt="HVTrust"></a>
Other agents in Agent Skills
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON