← Home

disparity

Colorized string diff ideal for text/code that spans through multiple lines

9
Versions
MIT
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

ruyadornomillermedeiros

Keywords

diffcharunifiedmultilinestringcoloransiterminalclitty

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition to ruyadorno (trusted npm maintainer, former npm CLI team) in 2019. Stable for this package. ai
email-domain unclaimed-email:http://millermedeiros.com AI (email-domain): Author field contains a URL (http://millermedeiros.com), not an email. Parser false positive; not a real domain hijack vector for npm identity. ai
maintainer-change maintainer-added AI (maintainer-change): ruyadorno is a highly trusted npm publisher (ex-npm CLI team); legitimate maintainer addition for this package. ai

Versions (showing 9 of 9)

Version Deps Published
3.2.0 2 / 0
3.1.0 2 / 0
3.0.0 2 / 0
2.0.0 2 / 0
1.3.1 2 / 0
1.3.0 2 / 0
1.2.0 3 / 0
1.1.0 3 / 0
1.0.0 3 / 0

v3.2.0

2 findings
HIGH Unclaimed maintainer email domain: http://millermedeiros.com email-domain

Maintainer email 'http://millermedeiros.com' uses domain 'http://millermedeiros.com' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v3.1.0

1 finding
LOW No provenance attestation provenance

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

v3.0.0

2 findings
HIGH Publisher changed: millermedeiros → ruyadorno (on 2019-11-06) provenance

This version was published by a different npm account than previous versions on 2019-11-06. 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.

v2.0.0

1 finding
LOW No provenance attestation provenance

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