← Home

readme-badger

npm Repository Homepage

Inserts badges into GitHub READMEs

6
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

mlmtrevorah

Keywords

badgebadgergithubreadme

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change (trevorah → mlm) occurred in 2017 within the same gitterHQ org context; repo URL unchanged, minimal diff, long-standing account — consistent with legitimate team handoff. ai
maintainer-change maintainer-added AI (maintainer-change): mlm added as maintainer in 2017 alongside the publisher change; same gitterHQ org context, no suspicious code changes, stable for this package. ai

Versions (showing 6 of 6)

Version Deps Published
0.3.0 1 / 1
0.2.0 0 / 1
0.1.2 0 / 1
0.1.1 0 / 1
0.1.0 0 / 1
0.0.1 0 / 1

v0.3.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.

v0.2.0

2 findings
HIGH Publisher changed: trevorah → mlm (on 2017-06-06) provenance

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

v0.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.1

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.