@propellerads/single-date-picker
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@propellerads/arrow-button | AI (dependencies): Same-org internal dependency; consistent with a component library monorepo pattern. | ai | |
| dependencies | unvetted-dep:@propellerads/button | AI (dependencies): Same-org internal dependency; consistent with a component library monorepo pattern. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Long-lived org package with no code changes vs prior approved version; dormancy likely reflects org release cadence, not takeover. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Internal UI component library; missing description is cosmetic and stable across versions. | ai | |
| phantom-deps | phantom-dep:@types/react-dates | AI (phantom-deps): Type-only package loaded by convention; not directly imported by design. | ai | |
| phantom-deps | phantom-dep:@propellerads/arrow-button | AI (phantom-deps): Same-org scoped package; indirect usage pattern is expected. | ai | |
| phantom-deps | phantom-dep:@propellerads/button | AI (phantom-deps): Same-org scoped package; indirect usage pattern is expected. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.0.0 | 6 / 6 | |
| 4.0.7 | 9 / 5 | |
| 4.0.6 | 9 / 5 | |
| 4.0.5 | 9 / 5 | |
| 4.0.4 | 9 / 5 | |
| 4.0.3 | 9 / 5 | |
| 4.0.2 | 9 / 5 | |
| 4.0.1 | 9 / 5 |
v4.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.