← Home

eslint-plugin-standard

npm Repository Homepage

ESlint Plugin for the Standard Linter

22
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

toddbluhmraynoswatsonjprichardsonmafintoshlinusufletferossbretxjamundx

Keywords

eslinteslintplugin

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate maintainer transition to feross (standard linter ecosystem author) in 2015; well-documented and long-standing. ai
provenance no-provenance AI (provenance): Package predates Sigstore provenance; no CI/CD provenance expected for 2015-era publishes. ai

Versions (showing 22 of 22)

Version Deps Published
5.0.0 0 / 3
4.1.0 0 / 3
4.0.2 0 / 3
4.0.1 0 / 3
4.0.0 0 / 3
3.1.0 0 / 3
3.0.1 0 / 3
3.0.0 0 / 3
2.3.1 0 / 3
2.3.0 0 / 3
2.2.0 0 / 3
2.1.1 0 / 3
2.1.0 0 / 3
2.0.1 0 / 2
2.0.0 0 / 2
1.3.3 0 / 2
1.3.2 0 / 2
1.3.1 0 / 2
1.3.0 0 / 4
1.2.0 1 / 4
1.1.0 1 / 4
1.0.0 1 / 3

v4.1.0

1 finding
INFO No provenance attestation provenance

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

v4.0.2

1 finding
INFO No provenance attestation provenance

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

v4.0.1

1 finding
INFO No provenance attestation provenance

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

v4.0.0

1 finding
INFO No provenance attestation provenance

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

v1.3.1

2 findings
HIGH Publisher changed: xjamundx → feross (on 2015-09-16) provenance

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