eslint-plugin-flowtype
Flowtype linting rules for ESLint.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package by known publisher gajus; lack of Sigstore provenance is common for packages of this age and does not indicate risk. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 8.0.3 | 2 / 21 | |
| 8.0.2 | 2 / 21 | |
| 8.0.1 | 2 / 21 | |
| 8.0.0 | 2 / 20 | |
| 7.0.0 | 2 / 21 | |
| 4.7.0 | 1 / 18 | |
| 3.10.3 | 1 / 16 |
v8.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.