@voiceflow/eslint-config
Shared configuration for [`eslint`](https://eslint.org/).
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:eslint-formatter-junit | AI (dependencies): Known ESLint formatter package; no malicious indicators, stable ecosystem tool. | ai | |
| dependencies | unvetted-dep:eslint-formatter-stylish | AI (dependencies): Known ESLint formatter package; no malicious indicators, stable ecosystem tool. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): ESLint config packages reference plugins/configs by name in config objects, not via import statements — stable FP for this package. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): ESLint config packages reference resolvers by name in config objects, not via import statements — stable FP for this package. | ai |
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 7.19.1 | 21 / 0 | |
| 7.19.0 | 21 / 0 | |
| 7.18.5 | 21 / 0 | |
| 7.18.4 | 21 / 2 | |
| 7.18.3 | 21 / 2 | |
| 7.18.2 | 21 / 2 | |
| 7.18.1 | 21 / 2 | |
| 7.18.0 | 21 / 2 | |
| 7.17.0 | 19 / 2 | |
| 7.16.3 | 19 / 2 | |
| 7.16.2 | 19 / 2 | |
| 7.16.1 | 19 / 2 | |
| 7.16.0 | 19 / 2 | |
| 7.15.0 | 19 / 2 | |
| 7.14.0 | 20 / 2 | |
| 7.13.0 | 20 / 2 | |
| 7.12.0 | 20 / 2 | |
| 7.11.0 | 20 / 1 | |
| 7.10.2 | 20 / 1 |
v7.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.