@mirohq/design-system-calendar

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

ivanbanov.mirokaren.nmirohq-admin

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	2026/05/21
npm-metadata	no-description	AI (npm-metadata): Miro internal design system component; empty description is a monorepo convention.	ai	2026/05/21
dependencies	unvetted-dep:@mirohq/design-system-flex	AI (dependencies): Internal Miro design system sibling package; part of established monorepo.	ai	2026/05/21
dependencies	unvetted-dep:@mirohq/design-system-types	AI (dependencies): Internal Miro design system sibling package; part of established monorepo.	ai	2026/05/21
dependencies	unvetted-dep:@mirohq/design-system-utils	AI (dependencies): Internal Miro design system sibling package; part of established monorepo.	ai	2026/05/21
dependencies	unvetted-dep:@mirohq/design-system-button	AI (dependencies): Internal Miro design system sibling package; part of established monorepo.	ai	2026/05/21
dependencies	unvetted-dep:@mirohq/design-system-styles	AI (dependencies): Internal Miro design system sibling package; part of established monorepo.	ai	2026/05/21
dependencies	unvetted-dep:@mirohq/design-system-tooltip	AI (dependencies): Internal Miro design system sibling package; part of established monorepo.	ai	2026/05/21
dependencies	unvetted-dep:@mirohq/design-system-stitches	AI (dependencies): Internal Miro design system sibling package; part of established monorepo.	ai	2026/05/21
dependencies	unvetted-dep:@mirohq/design-system-base-form	AI (dependencies): Internal Miro design system sibling package; part of established monorepo.	ai	2026/05/21
dependencies	unvetted-dep:@mirohq/design-system-primitive	AI (dependencies): Internal Miro design system sibling package; part of established monorepo.	ai	2026/05/21
dependencies	unvetted-dep:@mirohq/design-system-typography	AI (dependencies): Internal Miro design system sibling package; part of established monorepo.	ai	2026/05/21
dependencies	unvetted-dep:@mirohq/design-system-base-button	AI (dependencies): Internal Miro design system sibling package; part of established monorepo.	ai	2026/05/21
dependencies	unvetted-dep:@mirohq/design-system-icon-button	AI (dependencies): Internal Miro design system sibling package; part of established monorepo.	ai	2026/05/21
phantom-deps	phantom-dep:@react-types/shared	AI (phantom-deps): Type-only dependency referenced in config/type declarations; not a runtime import.	ai	2026/05/21
phantom-deps	phantom-dep:@react-types/datepicker	AI (phantom-deps): Type-only dependency referenced in config/type declarations; not a runtime import.	ai	2026/05/21
bogus-package	bogus-package	AI (bogus-package): Miro internal design system component; missing metadata is a monorepo convention, not a spam indicator.	ai	2026/05/21

Versions (showing 51 of 100)

View all versions

Version	Deps	Published
2.4.25	21 / 0	2026-06-08
2.4.24	21 / 0	2026-06-03
2.4.23	21 / 0	2026-05-29
2.4.22	21 / 0	2026-05-28
2.4.21	21 / 0	2026-05-22
2.4.20	21 / 0	2026-05-15
2.4.19	21 / 0	2026-05-11
2.4.18	21 / 0	2026-05-07
2.4.17	21 / 0	2026-05-07
2.4.16	21 / 0	2026-04-29
2.4.14	21 / 0	2026-04-28
2.4.13	21 / 0	2026-04-28
2.4.12	21 / 0	2026-04-27
2.4.11	21 / 0	2026-04-23
2.4.10	21 / 0	2026-04-23
2.4.9	21 / 0	2026-04-22
2.4.8	21 / 0	2026-04-22
2.4.7	21 / 0	2026-04-20
2.4.6	21 / 0	2026-04-17
2.4.5	21 / 0	2026-04-16
2.4.4	21 / 0	2026-04-13
2.4.3	21 / 0	2026-04-10
2.4.2	21 / 0	2026-04-07
2.4.1	21 / 0	2026-04-02
2.4.0	21 / 0	2026-04-02
2.3.16	21 / 0	2026-03-31
2.3.15	21 / 0	2026-03-24
2.3.14	21 / 0	2026-03-24
2.3.13	21 / 0	2026-03-24
2.3.12	21 / 0	2026-03-24
2.3.11	21 / 0	2026-03-23
2.3.10	21 / 0	2026-03-23
2.3.9	21 / 0	2026-03-23
2.3.8	21 / 0	2026-03-20
2.3.7	21 / 0	2026-03-19
2.3.6	21 / 0	2026-03-18
2.3.5	21 / 0	2026-03-18
2.3.4	21 / 0	2026-03-18
2.3.3	21 / 0	2026-03-13
2.3.2	21 / 0	2026-03-10
2.3.1	21 / 0	2026-03-10
2.3.0	21 / 0	2026-03-09
2.2.12	21 / 0	2026-03-09
2.2.11	21 / 0	2026-03-03
2.2.10	21 / 0	2026-03-02
2.2.9	21 / 0	2026-02-26
2.2.8	21 / 0	2026-02-11
2.2.7	21 / 0	2026-02-09
2.2.6	21 / 0	2026-02-05
2.2.5	21 / 0	2026-02-05
2.2.4	21 / 0	2026-01-26

v2.4.25

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.24

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.23

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.22

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.21

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.16

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.4.1

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.16

1 finding

INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.3.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.3.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.