react-flatpickr
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.0.11 | 1 / 36 | |
| 4.0.10 | 1 / 36 | |
| 4.0.3 | 1 / 34 | |
| 4.0.2 | 1 / 33 | |
| 4.0.1 | 2 / 26 | |
| 4.0.0 | 2 / 22 |
v4.0.3
2 findingsThis version was published by a different npm account than previous versions on 2025-04-16. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (haoxins) than the most recent previously approved version (jacobmischka) on 2025-04-11, but haoxins is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (haoxins) than the most recent previously approved version (jacobmischka) on 2025-04-06, but haoxins is listed as a maintainer on prior approved versions (matched on email). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.