@akinon/ui-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, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal scoped org package; missing metadata is consistent across all @akinon packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Stable pattern across @akinon scoped packages; not indicative of malice. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 1.5.4 | 6 / 6 | |
| 1.5.3 | 6 / 6 | |
| 1.5.2 | 6 / 6 | |
| 1.5.1 | 6 / 6 | |
| 1.5.0 | 6 / 6 | |
| 1.4.10 | 6 / 6 | |
| 1.4.9 | 6 / 6 | |
| 1.4.8 | 6 / 6 | |
| 1.4.7 | 6 / 6 | |
| 1.4.6 | 6 / 6 | |
| 1.4.5 | 6 / 6 | |
| 1.4.4 | 6 / 6 | |
| 1.4.3 | 6 / 6 | |
| 1.4.2 | 6 / 6 | |
| 1.4.1 | 6 / 6 | |
| 1.4.0 | 6 / 6 | |
| 1.3.2 | 6 / 6 | |
| 1.3.1 | 6 / 6 | |
| 1.3.0 | 6 / 6 | |
| 1.2.1 | 4 / 6 | |
| 1.2.0 | 4 / 6 | |
| 1.1.0 | 4 / 6 | |
| 1.0.1 | 3 / 7 | |
| 1.0.0 | 3 / 7 |
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.