Feishu Docx
🚀 Feishu/Lark Docs、Sheet、Bitable <-> Markdown | AI Agent-friendly knowledge base exporter and writer with OAuth 2.0, CLI, TUI & Claude Skills support - 飞书文档 <写入/导出> Markdown | AI Agent 友好型导出-写入工具
Is Feishu Docx safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Feishu Docx
How does it stack up against its Agent Skills neighbours?
Pick any agent to compare →In detail: Feishu Docx scores 54.8/100 (Grade C), ranked #177 of 371 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 4.5/10; 25% of recent commits are signed; no published advisory affects its latest release (feishu-docx); last pushed 2026-09-23. Every point is earned from checkable signals — never paid placement. How scoring works →
How Feishu Docx could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesPyPI Trusted Publishing attestations +14.7 → 69.5 B · #33 of 371
- Raise the OSSF Scorecard from 4.5 to 9.0lowest checks: Branch-Protection 0, CI-Tests 0, CII-Best-Practices 0 +9.4 → 64.2 C · #66 of 371
- Sign every commit25% signed today +3.7 → 58.5 C · #123 of 371
Chain of custody
Scanners check what the code says. This traces who ships Feishu Docx and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities and, for skills, AST02 Supply Chain Compromise.
-
Source Partly signed
github.com/leemysw/feishu-docx, MIT, last pushed 2026-09-23. 25% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Mixed
OpenSSF Scorecard rates the repository's practices 4.5/10 (scanned Oct 10, 2026). The checks that decide who can get a change released:
- Code Review5
- Branch Protection0
- Signed Releasesn/a
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests 0CII-Best-Practices 0Code-Review 5Contributors 10Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging -1Pinned-Dependencies 0SAST 0Security-Policy 0Signed-Releases -1Token-Permissions 0Vulnerabilities 10 -
Published packages Linked, not attested
- PyPI feishu-docx Source link points back to this repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
-
What you install today No known advisories
Latest release checked: feishu-docx 0.2.8. No published advisory affects it (OSV, checked 2026-10-14).
Changes to this chain
- 2026-08-29 OSSF Scorecard: 4.5/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Feishu Docx’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read the skill’s instructions for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you install it, such as Cisco Skill Scanner.
How Feishu Docx compares in Agent Skills
- #175 Fireworks Tech Graph 54.9 +0.1
- #176 Android Skills 54.8 ±0
- #177 Feishu Docx 54.8 this agent
- #178 Claude Obsidian 54.7 −0.1
- #179 Html Anything 54.7 −0.1
Bars show each HVTrust score; the tick marks Feishu Docx’s 54.8.
Where the 54.8 comes from
HVTrust dimensions vs the Agent Skills average
54.8 / 100 · 100.0% confidenceFeishu Docx Agent Skills average (371 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 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
50.3 / 100Common questions about Feishu Docx
Does Feishu Docx publish package provenance?
Does Feishu Docx have an OpenSSF Scorecard?
Is Feishu Docx actively maintained?
What license does Feishu Docx use?
Are Feishu Docx'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 →
- browser
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Maintain Feishu Docx?
For maintainers
HVTrust scores Feishu Docx 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/feishu-docx)
<a href="https://hvtracker.net/agents/feishu-docx"><img src="https://hvtracker.net/badge/feishu-docx.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.4 · Raw JSON