@aiou/eslint-config
eslint config for JW
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@aiou/eslint-ignore | AI (dependencies): Same author namespace (@aiou); present in prior approved versions of this config package. | ai | |
| dependencies | unvetted-dep:eslint-plugin-import-newlines | AI (dependencies): Well-known ESLint plugin; consistent with this package's purpose and present across versions. | ai | |
| provenance | no-provenance | AI (provenance): Established package with 135 versions; lack of provenance is common and not a risk signal here. | ai | |
| phantom-deps | phantom-dep:yaml-eslint-parser | AI (phantom-deps): Parser referenced in ESLint flat config objects, not imported via require/import — stable false positive for config packages. | ai | |
| phantom-deps | phantom-dep:jsonc-eslint-parser | AI (phantom-deps): Same pattern: parser passed as config value, not directly imported — stable false positive for config packages. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.1.2 | 28 / 16 | |
| 3.1.1 | 29 / 16 | |
| 3.1.0 | 29 / 16 | |
| 3.0.2 | 29 / 16 | |
| 3.0.1 | 29 / 16 | |
| 3.0.0 | 29 / 16 |
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.