@simplybusiness/mobius-datepicker
Mobius date picker component
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:@simplybusiness/icons | AI (dependencies): Internal sibling package from same org monorepo; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@simplybusiness/mobius | AI (dependencies): Internal sibling package from same org monorepo; expected dependency pattern. | ai | |
| dependencies | unvetted-dep:@simplybusiness/mobius-hooks | AI (dependencies): Internal sibling package from same org monorepo; expected dependency pattern. | ai |
Versions (showing 68 of 68)
| Version | Deps | Published |
|---|---|---|
| 10.0.16 | 6 / 31 | |
| 10.0.15 | 6 / 31 | |
| 10.0.14 | 6 / 31 | |
| 10.0.13 | 6 / 30 | |
| 10.0.12 | 6 / 30 | |
| 10.0.11 | 6 / 30 | |
| 10.0.10 | 6 / 30 | |
| 10.0.9 | 6 / 30 | |
| 10.0.8 | 6 / 30 | |
| 10.0.7 | 6 / 30 | |
| 10.0.6 | 6 / 30 | |
| 10.0.5 | 6 / 30 | |
| 10.0.4 | 6 / 30 | |
| 10.0.3 | 6 / 30 | |
| 10.0.2 | 6 / 30 | |
| 10.0.1 | 6 / 30 | |
| 10.0.0 | 6 / 30 | |
| 9.1.4 | 6 / 30 | |
| 9.1.3 | 6 / 30 | |
| 9.1.2 | 6 / 30 | |
| 9.1.1 | 6 / 30 | |
| 9.1.0 | 6 / 30 | |
| 9.0.9 | 6 / 30 | |
| 9.0.8 | 6 / 30 | |
| 9.0.7 | 6 / 30 | |
| 9.0.6 | 6 / 30 | |
| 9.0.5 | 6 / 30 | |
| 9.0.4 | 6 / 30 | |
| 9.0.3 | 6 / 30 | |
| 9.0.2 | 5 / 35 | |
| 9.0.1 | 5 / 35 | |
| 9.0.0 | 5 / 35 | |
| 8.0.4 | 5 / 35 | |
| 8.0.3 | 5 / 35 | |
| 8.0.2 | 5 / 35 | |
| 8.0.1 | 5 / 35 | |
| 8.0.0 | 5 / 35 | |
| 7.3.17 | 5 / 35 | |
| 7.3.16 | 5 / 35 | |
| 7.3.15 | 5 / 35 | |
| 7.3.14 | 5 / 35 | |
| 7.3.13 | 5 / 35 | |
| 7.3.12 | 5 / 35 | |
| 7.3.11 | 5 / 35 | |
| 7.3.10 | 5 / 35 | |
| 7.3.9 | 5 / 35 | |
| 7.3.8 | 5 / 35 | |
| 7.3.7 | 5 / 35 | |
| 7.3.6 | 5 / 35 | |
| 7.3.5 | 5 / 35 | |
| 7.3.4 | 5 / 35 | |
| 7.3.3 | 5 / 35 | |
| 7.3.2 | 5 / 35 | |
| 7.3.1 | 5 / 35 | |
| 7.3.0 | 5 / 35 | |
| 7.2.1 | 5 / 35 | |
| 7.2.0 | 5 / 35 | |
| 7.1.25 | 5 / 36 | |
| 7.1.24 | 5 / 36 | |
| 7.1.23 | 5 / 36 | |
| 7.1.22 | 5 / 36 | |
| 7.1.21 | 5 / 36 | |
| 7.1.20 | 5 / 36 | |
| 7.1.19 | 5 / 36 | |
| 7.1.18 | 5 / 36 | |
| 7.1.17 | 5 / 36 | |
| 7.1.16 | 5 / 36 | |
| 7.1.15 | 5 / 36 |
v10.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.1.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.