← Home

@superdoc-dev/mcp

npm

MCP server for SuperDoc. Lets AI agents open, read, edit, and save `.docx` files through the [Model Context Protocol](https://modelcontextprotocol.io).

29
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

falsaadehharbournickcaio-pizzol

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@superdoc-dev/sdk AI (phantom-deps): Same-org sibling package, used indirectly. ai
provenance missing-githead AI (provenance): Manual publish by known maintainer, consistent with prior pattern. ai
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 29 of 29)

Version Deps Published
1.0.0 2 / 6
0.17.1 3 / 6
0.17.0 3 / 6
0.16.2 3 / 6
0.16.1 3 / 6
0.16.0 3 / 6
0.15.2 2 / 6
0.15.1 2 / 6
0.15.0 2 / 6
0.14.0 2 / 6
0.13.0 2 / 6
0.12.1 2 / 6
0.12.0 2 / 6
0.11.0 2 / 6
0.10.0 2 / 6
0.9.0 2 / 6
0.8.1 2 / 6
0.8.0 2 / 6
0.7.0 2 / 6
0.6.1 2 / 6
0.6.0 2 / 6
0.5.1 2 / 6
0.5.0 2 / 6
0.4.0 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.17.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.17.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.16.0

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: caio-pizzol.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: harbournick → caio-pizzol (on 2026-07-05, known maintainer) provenance

This version was published by a different npm account (caio-pizzol) than the most recent previously approved version (harbournick) on 2026-07-05, but caio-pizzol is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.15.2

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: caio-pizzol.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: harbournick → caio-pizzol (on 2026-06-26, known maintainer) provenance

This version was published by a different npm account (caio-pizzol) than the most recent previously approved version (harbournick) on 2026-06-26, but caio-pizzol is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.10.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.6.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: harbournick.

v0.5.0

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: harbournick.