← Home

eslint-config-standard-jsx

JavaScript Standard Style JSX support - ESLint Shareable Config

27
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

jhieseybretferossfletlinusumafintoshjprichardsonwatsonraynostoddbluhmvoxpelli

Keywords

JavaScript Standard Stylecheckcheckercodecode checkercode lintercode standardscode styleenforceeslinteslintconfighintjscsjshintjsxlintpolicyqualitysimplestandardstandard stylestylestyle checkerstyle linterverify

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Documented transition from feross to voxpelli within the standard org. voxpelli has a strong track record (812/0) and the repo URL is consistent with the standard GitHub org. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainers are well-known standard ecosystem contributors; reflects a legitimate org-level maintainer restructuring, not a hostile takeover. ai

Versions (showing 27 of 27)

Version Deps Published
11.0.0 0 / 5
10.0.0 0 / 3
9.0.0 0 / 3
8.1.0 0 / 3
8.0.1 0 / 3
8.0.0 0 / 3
7.0.0 0 / 3
6.0.2 0 / 3
6.0.1 0 / 3
6.0.0 0 / 3
5.0.0 0 / 3
4.0.2 0 / 3
4.0.1 0 / 3
4.0.0 0 / 3
3.3.0 0 / 3
3.2.0 0 / 3
3.1.0 0 / 3
3.0.1 0 / 3
3.0.0 0 / 3
2.0.0 0 / 3
1.2.2 0 / 3
1.2.1 0 / 3
1.2.0 0 / 3
1.1.1 0 / 3
1.1.0 0 / 3
1.0.1 0 / 1
1.0.0 0 / 1

v11.0.0

2 findings
HIGH Publisher changed: feross → voxpelli (on 2022-04-20) provenance

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

v10.0.0

1 finding
LOW No provenance attestation provenance

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