← Home

diff-match-patch

npm Repository Homepage

npm package for https://github.com/google/diff-match-patch

6
Versions
Apache-2.0
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

forbeslindesayjackub

Keywords

diffdiff-match-patchgoogle-diff-match-patch

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change from forbeslindesay to jackub (JackuB) is a legitimate handoff confirmed by the GitHub repo URL matching the new publisher's identity. Occurred in 2018; 6 subsequent versions all approved. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainer jackub aligns with the GitHub repo owner JackuB; legitimate transition confirmed by repo URL and clean version history since 2018. ai

Versions (showing 6 of 6)

Version Deps Published
1.0.5 0 / 1
1.0.4 0 / 1
1.0.3 0 / 1
1.0.2 0 / 1
1.0.1 0 / 1
1.0.0 0 / 1

v1.0.5

1 finding
LOW No provenance attestation provenance

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

v1.0.4

1 finding
LOW No provenance attestation provenance

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

v1.0.3

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

2 findings
HIGH Publisher changed: forbeslindesay → jackub (on 2018-05-08) provenance

This version was published by a different npm account than previous versions on 2018-05-08. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v1.0.0

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.