@dfds-ui/dates
Date components
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:dayjs | AI (typosquat): Scoped @dfds-ui/ package; not a typosquat of dayjs, just a date-related component in the DFDS UI library. | ai | |
| phantom-deps | phantom-dep:@dfds-ui/colors | AI (phantom-deps): Same-org sibling dep; may be used transitively or in type declarations rather than direct imports. | ai | |
| phantom-deps | phantom-dep:@dfds-ui/typography | AI (phantom-deps): Same-org sibling dep; may be used transitively or in type declarations rather than direct imports. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.2.1 | 10 / 0 | |
| 2.0.29 | 10 / 0 | |
| 2.0.28 | 10 / 0 | |
| 2.0.27 | 10 / 0 | |
| 2.0.26 | 10 / 0 | |
| 2.0.25 | 10 / 0 | |
| 2.0.24 | 10 / 0 |
v2.0.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.