@mirohq/design-system-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 — 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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Miro design-system packages consistently lack provenance; not a risk signal for this org. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Miro internal design system component; empty description is a monorepo convention. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-flex | AI (dependencies): Internal Miro design system sibling package; part of established monorepo. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-types | AI (dependencies): Internal Miro design system sibling package; part of established monorepo. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-utils | AI (dependencies): Internal Miro design system sibling package; part of established monorepo. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-button | AI (dependencies): Internal Miro design system sibling package; part of established monorepo. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-styles | AI (dependencies): Internal Miro design system sibling package; part of established monorepo. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-tooltip | AI (dependencies): Internal Miro design system sibling package; part of established monorepo. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-stitches | AI (dependencies): Internal Miro design system sibling package; part of established monorepo. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-form | AI (dependencies): Internal Miro design system sibling package; part of established monorepo. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-primitive | AI (dependencies): Internal Miro design system sibling package; part of established monorepo. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-typography | AI (dependencies): Internal Miro design system sibling package; part of established monorepo. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-button | AI (dependencies): Internal Miro design system sibling package; part of established monorepo. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-icon-button | AI (dependencies): Internal Miro design system sibling package; part of established monorepo. | ai | |
| phantom-deps | phantom-dep:@react-types/shared | AI (phantom-deps): Type-only dependency referenced in config/type declarations; not a runtime import. | ai | |
| phantom-deps | phantom-dep:@react-types/datepicker | AI (phantom-deps): Type-only dependency referenced in config/type declarations; not a runtime import. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Miro internal design system component; missing metadata is a monorepo convention, not a spam indicator. | ai |
Versions (showing 100 of 100)
| Version | Deps | Published |
|---|---|---|
| 2.4.25 | 21 / 0 | |
| 2.4.24 | 21 / 0 | |
| 2.4.23 | 21 / 0 | |
| 2.4.22 | 21 / 0 | |
| 2.4.21 | 21 / 0 | |
| 2.4.20 | 21 / 0 | |
| 2.4.19 | 21 / 0 | |
| 2.4.18 | 21 / 0 | |
| 2.4.17 | 21 / 0 | |
| 2.4.16 | 21 / 0 | |
| 2.4.14 | 21 / 0 | |
| 2.4.13 | 21 / 0 | |
| 2.4.12 | 21 / 0 | |
| 2.4.11 | 21 / 0 | |
| 2.4.10 | 21 / 0 | |
| 2.4.9 | 21 / 0 | |
| 2.4.8 | 21 / 0 | |
| 2.4.7 | 21 / 0 | |
| 2.4.6 | 21 / 0 | |
| 2.4.5 | 21 / 0 | |
| 2.4.4 | 21 / 0 | |
| 2.4.3 | 21 / 0 | |
| 2.4.2 | 21 / 0 | |
| 2.4.1 | 21 / 0 | |
| 2.4.0 | 21 / 0 | |
| 2.3.16 | 21 / 0 | |
| 2.3.15 | 21 / 0 | |
| 2.3.14 | 21 / 0 | |
| 2.3.13 | 21 / 0 | |
| 2.3.12 | 21 / 0 | |
| 2.3.11 | 21 / 0 | |
| 2.3.10 | 21 / 0 | |
| 2.3.9 | 21 / 0 | |
| 2.3.8 | 21 / 0 | |
| 2.3.7 | 21 / 0 | |
| 2.3.6 | 21 / 0 | |
| 2.3.5 | 21 / 0 | |
| 2.3.4 | 21 / 0 | |
| 2.3.3 | 21 / 0 | |
| 2.3.2 | 21 / 0 | |
| 2.3.1 | 21 / 0 | |
| 2.3.0 | 21 / 0 | |
| 2.2.12 | 21 / 0 | |
| 2.2.11 | 21 / 0 | |
| 2.2.10 | 21 / 0 | |
| 2.2.9 | 21 / 0 | |
| 2.2.8 | 21 / 0 | |
| 2.2.7 | 21 / 0 | |
| 2.2.6 | 21 / 0 | |
| 2.2.5 | 21 / 0 | |
| 2.2.4 | 21 / 0 | |
| 2.2.3 | 21 / 0 | |
| 2.2.2 | 21 / 0 | |
| 2.2.1 | 21 / 0 | |
| 2.2.0 | 21 / 0 | |
| 2.1.20 | 21 / 0 | |
| 2.1.19 | 21 / 0 | |
| 2.1.18 | 21 / 0 | |
| 2.1.17 | 21 / 0 | |
| 2.1.16 | 21 / 0 | |
| 2.1.15 | 21 / 0 | |
| 2.1.14 | 21 / 0 | |
| 2.1.13 | 21 / 0 | |
| 2.1.12 | 21 / 0 | |
| 2.1.11 | 21 / 0 | |
| 2.1.10 | 21 / 0 | |
| 2.1.9 | 21 / 0 | |
| 2.1.8 | 21 / 0 | |
| 2.1.7 | 21 / 0 | |
| 2.1.6 | 21 / 0 | |
| 2.1.5 | 21 / 0 | |
| 2.1.4 | 21 / 0 | |
| 2.1.3 | 21 / 0 | |
| 2.1.2 | 21 / 0 | |
| 2.1.1 | 21 / 0 | |
| 2.1.0 | 21 / 0 | |
| 2.0.23 | 21 / 0 | |
| 2.0.22 | 21 / 0 | |
| 2.0.21 | 21 / 0 | |
| 2.0.20 | 21 / 0 | |
| 2.0.19 | 21 / 0 | |
| 2.0.18 | 21 / 0 | |
| 2.0.17 | 21 / 0 | |
| 2.0.16 | 21 / 0 | |
| 2.0.15 | 21 / 0 | |
| 2.0.14 | 21 / 0 | |
| 2.0.13 | 21 / 0 | |
| 2.0.12 | 21 / 0 | |
| 2.0.11 | 21 / 0 | |
| 2.0.10 | 21 / 0 | |
| 2.0.9 | 21 / 0 | |
| 2.0.8 | 21 / 0 | |
| 2.0.7 | 21 / 0 | |
| 2.0.6 | 21 / 0 | |
| 2.0.5 | 21 / 0 | |
| 2.0.4 | 21 / 0 | |
| 2.0.3 | 21 / 0 | |
| 2.0.2 | 21 / 0 | |
| 2.0.1 | 21 / 0 | |
| 2.0.0 | 21 / 0 |
v2.4.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.