@superdoc-dev/mcp
MCP server for SuperDoc. Lets AI agents open, read, edit, and save `.docx` files through the [Model Context Protocol](https://modelcontextprotocol.io).
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | encoded-string-file:dist/index.js | AI (source-diff): Encoded string is htmlDecodeTree base64 data from the entities package bundled into dist — benign and expected. | ai | |
| typosquat | typosquat.levenshtein:yup | AI (typosquat): Scoped package @superdoc-dev/mcp is an MCP server for the SuperDoc project; Levenshtein match to 'yup' is a false positive with no plausible impersonation scenario. | ai | |
| phantom-deps | phantom-dep:zod | AI (phantom-deps): Package is compiled with bun build into dist/; source-level imports are bundled away, making phantom-dep detection unreliable for this package. | ai | |
| phantom-deps | phantom-dep:@modelcontextprotocol/sdk | AI (phantom-deps): Same as zod — compiled/bundled output means source imports are not visible to the analyzer; false positive for this build pattern. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.0.0 | 2 / 6 | |
| 0.5.1 | 2 / 6 | |
| 0.3.1 | 2 / 6 | |
| 0.3.0 | 2 / 6 | |
| 0.2.0 | 4 / 5 | |
| 0.1.1 | 2 / 6 | |
| 0.1.0 | 2 / 6 |
v0.5.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: harbournick.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: harbournick.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: harbournick.
Modified file contains 1 long encoded string(s) (200+ chars). These are commonly used to hide malicious payloads.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.