← Home

@vidispine/eslint-config-react

npm Repository Homepage
8
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

vidispine-ownertinyeengl.degenermatthiaspeinevidispineulrichenraafeyozl

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:eslint-plugin-react AI (phantom-deps): ESLint config packages reference plugins in config, not via import; stable false positive for this package type. ai
phantom-deps phantom-dep:eslint-config-airbnb AI (phantom-deps): ESLint config packages reference configs in config, not via import; stable false positive. ai
phantom-deps phantom-dep:eslint-plugin-import AI (phantom-deps): ESLint config packages reference plugins in config, not via import; stable false positive. ai
phantom-deps phantom-dep:eslint-plugin-jsx-a11y AI (phantom-deps): ESLint config packages reference plugins in config, not via import; stable false positive. ai
phantom-deps phantom-dep:eslint-plugin-react-hooks AI (phantom-deps): ESLint config packages reference plugins in config, not via import; stable false positive. ai
phantom-deps phantom-dep:eslint-plugin-react-refresh AI (phantom-deps): ESLint config packages reference plugins in config, not via import; stable false positive. ai
phantom-deps phantom-dep:@vidispine/eslint-config-base AI (phantom-deps): Same-org sibling config package; referenced in config not via import; stable false positive. ai

Versions (showing 8 of 8)

Version Deps Published
26.1.0 7 / 4
25.4.6 7 / 4
25.4.5 7 / 4
25.4.4 7 / 4
25.4.3 7 / 4
25.4.2 7 / 4
25.4.1 7 / 4
25.4.0 7 / 4

v26.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v25.4.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.4.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.4.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v25.4.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v25.4.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v25.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v25.4.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.