@snack-uikit/calendar
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Monorepo UI kit with 269 versions; gap likely reflects project cadence, not takeover. No material changes in diff. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentionally empty description in a monorepo UI kit; stable pattern across all versions. | ai |
Versions (showing 100 of 105)
| Version | Deps | Published |
|---|---|---|
| 0.14.2 | 8 / 0 | |
| 0.14.1 | 8 / 0 | |
| 0.14.0 | 8 / 0 | |
| 0.13.20 | 8 / 0 | |
| 0.13.19 | 8 / 0 | |
| 0.13.18 | 8 / 0 | |
| 0.13.17 | 8 / 0 | |
| 0.13.16 | 8 / 0 | |
| 0.13.15 | 8 / 0 | |
| 0.13.14 | 8 / 0 | |
| 0.13.13 | 8 / 0 | |
| 0.13.12 | 8 / 0 | |
| 0.13.11 | 8 / 0 | |
| 0.13.10 | 8 / 0 | |
| 0.13.9 | 8 / 0 | |
| 0.13.8 | 8 / 0 | |
| 0.13.7 | 8 / 0 | |
| 0.13.6 | 8 / 0 | |
| 0.13.5 | 8 / 0 | |
| 0.13.4 | 8 / 0 | |
| 0.13.3 | 8 / 0 | |
| 0.13.2 | 8 / 0 | |
| 0.13.1 | 8 / 0 | |
| 0.13.0 | 8 / 0 | |
| 0.12.20 | 8 / 0 | |
| 0.12.19 | 8 / 0 | |
| 0.12.18 | 8 / 0 | |
| 0.12.17 | 8 / 0 | |
| 0.12.16 | 8 / 0 | |
| 0.12.15 | 8 / 0 | |
| 0.12.14 | 8 / 0 | |
| 0.12.13 | 8 / 0 | |
| 0.12.12 | 8 / 0 | |
| 0.12.11 | 8 / 0 | |
| 0.12.10 | 8 / 0 | |
| 0.12.9 | 8 / 0 | |
| 0.12.8 | 8 / 0 | |
| 0.12.7 | 8 / 0 | |
| 0.12.6 | 8 / 0 | |
| 0.12.5 | 8 / 0 | |
| 0.12.4 | 8 / 0 | |
| 0.12.3 | 8 / 0 | |
| 0.12.2 | 8 / 0 | |
| 0.12.1 | 8 / 0 | |
| 0.12.0 | 8 / 0 | |
| 0.11.35 | 8 / 0 | |
| 0.11.34 | 8 / 0 | |
| 0.11.33 | 8 / 0 | |
| 0.11.32 | 8 / 0 | |
| 0.11.31 | 8 / 0 | |
| 0.11.30 | 8 / 0 | |
| 0.11.29 | 8 / 0 | |
| 0.11.28 | 8 / 0 | |
| 0.11.27 | 8 / 0 | |
| 0.11.26 | 8 / 0 | |
| 0.11.25 | 8 / 0 | |
| 0.11.24 | 8 / 0 | |
| 0.11.23 | 8 / 0 | |
| 0.11.22 | 8 / 0 | |
| 0.11.21 | 8 / 0 | |
| 0.11.20 | 8 / 0 | |
| 0.11.19 | 8 / 0 | |
| 0.11.18 | 8 / 0 | |
| 0.11.17 | 8 / 0 | |
| 0.11.16 | 8 / 0 | |
| 0.11.15 | 8 / 0 | |
| 0.11.14 | 8 / 0 | |
| 0.11.13 | 8 / 0 | |
| 0.11.12 | 8 / 0 | |
| 0.11.11 | 8 / 0 | |
| 0.11.10 | 8 / 0 | |
| 0.11.9 | 8 / 0 | |
| 0.11.8 | 8 / 0 | |
| 0.11.7 | 8 / 0 | |
| 0.11.6 | 8 / 0 | |
| 0.11.5 | 8 / 0 | |
| 0.11.4 | 8 / 0 | |
| 0.11.3 | 8 / 0 | |
| 0.11.2 | 8 / 0 | |
| 0.11.1 | 8 / 0 | |
| 0.11.0 | 8 / 0 | |
| 0.10.0 | 5 / 0 | |
| 0.9.0 | 5 / 0 | |
| 0.8.0 | 5 / 0 | |
| 0.7.12 | 5 / 0 | |
| 0.7.11 | 5 / 0 | |
| 0.7.10 | 5 / 0 | |
| 0.7.9 | 5 / 0 | |
| 0.7.8 | 5 / 0 | |
| 0.7.7 | 5 / 0 | |
| 0.7.6 | 5 / 0 | |
| 0.7.5 | 5 / 0 | |
| 0.7.4 | 6 / 0 | |
| 0.7.3 | 6 / 0 | |
| 0.7.2 | 6 / 0 | |
| 0.7.1 | 6 / 0 | |
| 0.7.0 | 6 / 0 | |
| 0.6.5 | 5 / 0 | |
| 0.6.4 | 5 / 0 | |
| 0.6.3 | 5 / 0 |
v0.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.