@vidispine/eslint-config
Eslint config for React apps
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@vidispine/eslint-config-base | AI (phantom-deps): Meta-package that re-exports same-org deps; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@vidispine/eslint-config-react | AI (phantom-deps): Meta-package that re-exports same-org deps; not directly imported by design. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 26.1.0 | 2 / 4 | |
| 25.4.6 | 2 / 4 | |
| 25.4.5 | 2 / 4 | |
| 25.4.4 | 2 / 4 | |
| 25.4.3 | 2 / 4 | |
| 25.4.2 | 2 / 4 | |
| 25.4.1 | 2 / 4 | |
| 25.4.0 | 2 / 4 |
v26.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.4.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v25.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v25.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.