← Home

@mulmoclaude/collection-plugin

npm Repository Homepage
49
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

snakajimaisamu

Keywords

collectionsschema-drivencrudmulmoclaudemulmoclaude-plugingui-chat-protocolclaude-codemulmoterminal

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff large-new-source-files AI (source-diff): New files are dist outputs for the added ./server export; consistent with legitimate feature addition. ai
source-diff source-size-tripled AI (source-diff): Size increase matches new server entry point dist files; no injected payload indicators. ai
publish-pattern new-deps-added AI (publish-pattern): zod is a well-established schema validation library; low risk addition. ai

Versions (showing 49 of 49)

Version Deps Published
1.2.1 2 / 12
1.2.0 2 / 12
1.1.1 2 / 12
1.1.0 2 / 12
1.0.2 2 / 12
1.0.1 2 / 12
1.0.0 2 / 12
0.15.0 2 / 12
0.14.1 2 / 12
0.14.0 2 / 12
0.13.2 2 / 11
0.13.1 2 / 11
0.13.0 2 / 11
0.12.0 2 / 11
0.11.4 2 / 11
0.11.3 2 / 11
0.11.2 2 / 11
0.11.1 2 / 11
0.11.0 2 / 11
0.8.0 2 / 11
0.7.6 2 / 11
0.7.5 2 / 11
0.7.4 2 / 11
0.7.3 2 / 11
0.7.2 2 / 11
0.7.1 2 / 11
0.7.0 2 / 11
0.6.0 2 / 11
0.5.21 2 / 11
0.5.20 2 / 11
0.5.18 2 / 11
0.5.17 2 / 11
0.5.16 2 / 11
0.5.11 2 / 11
0.5.9 2 / 11
0.5.8 2 / 10
0.5.7 2 / 10
0.5.6 2 / 10
0.5.3 2 / 10
0.5.2 2 / 10
0.5.1 2 / 10
0.5.0 2 / 10
0.4.1 2 / 10
0.4.0 2 / 10
0.3.0 2 / 10
0.2.2 1 / 5
0.2.1 1 / 5
0.2.0 1 / 5
0.1.0 0 / 4

v1.2.1

1 finding
LOW No provenance attestation provenance

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

v1.2.0

1 finding
LOW No provenance attestation provenance

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

v1.1.1

1 finding
LOW No provenance attestation provenance

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

v1.1.0

1 finding
LOW No provenance attestation provenance

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

v1.0.2

1 finding
LOW No provenance attestation provenance

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

v1.0.1

1 finding
LOW No provenance attestation provenance

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

v1.0.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: snakajima → isamu (on 2026-07-21, known maintainer) provenance

This version was published by a different npm account (isamu) than the most recent previously approved version (snakajima) on 2026-07-21, but isamu 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.0

1 finding
LOW No provenance attestation provenance

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

v0.14.1

1 finding
LOW No provenance attestation provenance

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

v0.14.0

1 finding
LOW No provenance attestation provenance

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

v0.13.2

1 finding
LOW No provenance attestation provenance

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

v0.13.1

1 finding
LOW No provenance attestation provenance

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

v0.13.0

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: isamu → snakajima (on 2026-07-19, known maintainer) provenance

This version was published by a different npm account (snakajima) than the most recent previously approved version (isamu) on 2026-07-19, but snakajima 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.12.0

1 finding
LOW No provenance attestation provenance

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

v0.11.4

1 finding
LOW No provenance attestation provenance

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

v0.11.3

1 finding
LOW No provenance attestation provenance

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

v0.11.2

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: snakajima → isamu (on 2026-07-16, known maintainer) provenance

This version was published by a different npm account (isamu) than the most recent previously approved version (snakajima) on 2026-07-16, but isamu 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.11.1

1 finding
LOW No provenance attestation provenance

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

v0.11.0

1 finding
LOW No provenance attestation provenance

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

v0.8.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.6

1 finding
LOW No provenance attestation provenance

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

v0.7.5

1 finding
LOW No provenance attestation provenance

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

v0.7.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: snakajima → isamu (on 2026-07-07, known maintainer) provenance

This version was published by a different npm account (isamu) than the most recent previously approved version (snakajima) on 2026-07-07, but isamu 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.7.3

1 finding
LOW No provenance attestation provenance

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

v0.7.2

1 finding
LOW No provenance attestation provenance

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

v0.7.1

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

1 finding
LOW No provenance attestation provenance

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

v0.5.21

1 finding
LOW No provenance attestation provenance

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

v0.5.20

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: isamu → snakajima (on 2026-06-28, known maintainer) provenance

This version was published by a different npm account (snakajima) than the most recent previously approved version (isamu) on 2026-06-28, but snakajima 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.5.18

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: isamu → snakajima (on 2026-06-28, known maintainer) provenance

This version was published by a different npm account (snakajima) than the most recent previously approved version (isamu) on 2026-06-28, but snakajima 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.5.17

1 finding
LOW No provenance attestation provenance

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

v0.5.16

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: snakajima → isamu (on 2026-06-28, known maintainer) provenance

This version was published by a different npm account (isamu) than the most recent previously approved version (snakajima) on 2026-06-28, but isamu 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.5.11

1 finding
LOW No provenance attestation provenance

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