@wordpress/eslint-plugin
ESLint plugin for WordPress development.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): Same ESLint config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): Same ESLint config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react-hooks | AI (phantom-deps): Same ESLint config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-jest | AI (phantom-deps): ESLint plugin packages reference peer plugins in config files, not via direct imports — stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-jsdoc | AI (phantom-deps): Same ESLint config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-react | AI (phantom-deps): Same ESLint config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@babel/eslint-parser | AI (phantom-deps): Framework-scoped parser loaded by convention in ESLint configs; stable false positive. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-import | AI (phantom-deps): Same ESLint config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): Same ESLint config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-jsx-a11y | AI (phantom-deps): Same ESLint config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-prettier | AI (phantom-deps): Same ESLint config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-playwright | AI (phantom-deps): Same ESLint config-reference pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@eslint-community/eslint-plugin-eslint-comments | AI (phantom-deps): ESLint plugin references other plugins in config files without direct imports; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): ESLint plugin references resolvers in config files without direct imports; stable false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 25.4.0 | 20 / 2 | |
| 25.3.0 | 20 / 2 | |
| 25.2.0 | 20 / 2 | |
| 25.1.0 | 20 / 2 | |
| 25.0.0 | 20 / 2 | |
| 24.5.0 | 19 / 2 | |
| 24.4.0 | 19 / 2 | |
| 24.3.0 | 19 / 2 | |
| 24.2.0 | 19 / 2 | |
| 24.1.0 | 19 / 2 | |
| 24.0.0 | 19 / 2 | |
| 23.0.0 | 18 / 0 | |
| 22.22.0 | 18 / 0 | |
| 22.21.0 | 18 / 0 |
v25.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v24.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v24.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v23.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v22.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.