@vidispine/eslint-config-typescript
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:eslint-plugin-import | AI (phantom-deps): ESLint config packages declare plugins as deps for consumers to inherit; not directly imported. | ai | |
| phantom-deps | phantom-dep:eslint-config-prettier | AI (phantom-deps): ESLint config packages declare configs as deps for consumers to inherit; not directly imported. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/parser | AI (phantom-deps): ESLint config packages declare parsers as deps for consumers to inherit; not directly imported. | ai | |
| phantom-deps | phantom-dep:eslint-config-airbnb-typescript | AI (phantom-deps): ESLint config packages declare configs as deps for consumers to inherit; not directly imported. | ai | |
| phantom-deps | phantom-dep:@typescript-eslint/eslint-plugin | AI (phantom-deps): ESLint config packages declare plugins as deps for consumers to inherit; not directly imported. | ai | |
| phantom-deps | phantom-dep:eslint-import-resolver-typescript | AI (phantom-deps): ESLint config packages declare resolvers as deps for consumers to inherit; not directly imported. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 26.1.0 | 6 / 5 | |
| 25.4.6 | 6 / 5 | |
| 25.4.5 | 6 / 5 | |
| 25.4.4 | 6 / 5 | |
| 25.4.3 | 6 / 5 | |
| 25.4.2 | 6 / 5 | |
| 25.4.1 | 6 / 5 | |
| 25.4.0 | 6 / 5 |
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.