OfficeCLI
OfficeCLI is the first and best Office suite purpose-built for AI agents to read, edit, and automate Word, Excel, and PowerPoint files. Free, open-source, single binary, no Office installation required.
Is OfficeCLI safe? Promising trust profile, but some evidence still deserves review.
Compare OfficeCLI
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: OfficeCLI scores 62.0/100 (Grade C), ranked #82 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 4.9/10; 8% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →
How OfficeCLI compares in Agent Skills
- #80 Claude Ads 62.3 +0.3
- #81 Linkedin Skills 62.1 +0.1
- #82 OfficeCLI 62.0 this agent
- #83 Antigravity For Claude Code 61.5 −0.5
- #84 Claude Obsidian 61.5 −0.5
Bars show each HVTrust score; the tick marks OfficeCLI’s 62.0.
Where the 62.0 comes from
HVTrust dimensions vs the Agent Skills average
62.0 / 100 · 100.0% confidenceOfficeCLI 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 C 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
91.0 / 100Supply Chain Trust
Common questions about OfficeCLI
Does OfficeCLI publish package provenance?
Does OfficeCLI have an OpenSSF Scorecard?
Is OfficeCLI actively maintained?
What license does OfficeCLI use?
Are OfficeCLI'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 OfficeCLI'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 OfficeCLI?
For maintainers
HVTrust scores OfficeCLI 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/officecli)
<a href="https://hvtracker.net/agents/officecli"><img src="https://hvtracker.net/badge/officecli.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