← Home

@fre4x/docx

npm

DOCX Editor MCP server

14
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

fritzprix

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:mobx AI (typosquat): Scoped DOCX/MCP package; name similarity to mobx is coincidental, not impersonation. ai
phantom-deps phantom-dep:zod AI (phantom-deps): Runtime dep bundled into dist/; not directly imported in source files. ai
phantom-deps phantom-dep:docx AI (phantom-deps): Runtime dep bundled into dist/; not directly imported in source files. ai
phantom-deps phantom-dep:mammoth AI (phantom-deps): Runtime dep bundled into dist/; not directly imported in source files. ai
phantom-deps phantom-dep:@modelcontextprotocol/sdk AI (phantom-deps): Runtime dep bundled into dist/; not directly imported in source files. ai

Versions (showing 14 of 14)

Version Deps Published
1.0.65 4 / 4
1.0.64 4 / 4
1.0.61 4 / 4
1.0.60 4 / 4
1.0.58 4 / 4
1.0.57 4 / 4
1.0.55 4 / 4
1.0.54 4 / 4
1.0.53 4 / 4
1.0.50 4 / 5
1.0.49 4 / 5
1.0.47 4 / 5
1.0.46 4 / 5
1.0.45 4 / 5

v1.0.65

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.64

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.61

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.60

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.58

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.57

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.55

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.54

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.53

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.50

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.49

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.47

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.46

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.0.45

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.