← Home

verb-readme-badges

npm Repository Homepage
10
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jonschlinkertdoowb

Keywords

badgebadgesboilerplatescodeclimatecoderwallcoverallsdaviddocsdocumentationdronefurygenerategithubincludemarkdownmdnpmprojectreadmerepotemplatetemplatestravisverbverbtemplate

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Publisher change jonschlinkert→doowb occurred in 2014 within the assemble/verb ecosystem; both are well-known, trusted npm maintainers. Historical transition, not a compromise. ai
maintainer-change maintainer-added AI (maintainer-change): doowb is a long-standing, trusted maintainer in the assemble/verb ecosystem with 1328 approved packages. Addition is a legitimate historical transition. ai
bogus-package bogus-package AI (bogus-package): verb-readme-badges is a badge template collection; no runtime deps and badge URLs in README are expected characteristics of this package type, not spam indicators. ai

Versions (showing 10 of 10)

Version Deps Published
0.2.0 0 / 0
0.1.2 0 / 0
0.1.1 0 / 0
0.1.0 0 / 0
0.0.6 0 / 0
0.0.5 0 / 0
0.0.4 0 / 0
0.0.3 0 / 0
0.0.2 0 / 0
0.0.1 0 / 0

v0.2.0

1 finding
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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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

2 findings
HIGH Publisher changed: jonschlinkert → doowb (on 2014-05-02) provenance

This version was published by a different npm account than previous versions on 2014-05-02. 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.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

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.0.3

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.0.2

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