@mirohq/design-system-link No license 41 versions

@mirohq/design-system-link

npm

41

Versions

—

License

No

Install Scripts

Missing

Provenance

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
dependencies	unvetted-dep:@mirohq/design-system-styles	AI (dependencies): Internal Miro design system sibling package; stable pattern across all versions.	ai	2026/05/17
dependencies	unvetted-dep:@mirohq/design-system-utils	AI (dependencies): Internal Miro design-system monorepo dep; stable pattern across all versions of this package.	ai	2026/05/17
dependencies	unvetted-dep:@mirohq/design-system-stitches	AI (dependencies): Internal Miro design-system monorepo dep; stable pattern across all versions of this package.	ai	2026/05/17
dependencies	unvetted-dep:@mirohq/design-system-use-press	AI (dependencies): Internal Miro design-system monorepo dep; stable pattern across all versions of this package.	ai	2026/05/17
bogus-package	bogus-package	AI (bogus-package): Miro org monorepo component; sparse metadata is consistent across all their design-system packages.	ai	2026/04/29
npm-metadata	no-description	AI (npm-metadata): Stable pattern across Miro design-system packages; not a spam indicator here.	ai	2026/04/29

Versions (showing 41 of 41)

Version	Deps	Published
2.5.19	8 / 0	2026-06-08
2.5.18	8 / 0	2026-05-28
2.5.17	8 / 0	2026-05-11
2.5.15	8 / 0	2026-05-07
2.5.14	8 / 0	2026-04-29
2.5.13	8 / 0	2026-04-29
2.5.12	8 / 0	2026-04-27
2.5.11	8 / 0	2026-04-23
2.5.10	8 / 0	2026-04-23
2.5.9	8 / 0	2026-04-22
2.5.8	8 / 0	2026-04-22
2.5.7	8 / 0	2026-04-20
2.5.6	8 / 0	2026-04-16
2.5.5	8 / 0	2026-04-13
2.5.4	8 / 0	2026-04-10
2.5.3	8 / 0	2026-04-07
2.5.2	8 / 0	2026-04-02
2.5.1	8 / 0	2026-03-24
2.5.0	8 / 0	2026-03-24
2.4.13	8 / 0	2026-03-23
2.4.12	8 / 0	2026-03-23
2.4.11	8 / 0	2026-03-20
2.4.10	8 / 0	2026-03-19
2.4.9	8 / 0	2026-03-18
2.4.8	8 / 0	2026-03-18
2.4.7	8 / 0	2026-03-18
2.4.6	8 / 0	2026-03-13
2.4.5	8 / 0	2026-03-10
2.4.4	8 / 0	2026-03-09
2.4.3	8 / 0	2026-03-03
2.4.2	8 / 0	2026-03-02
2.4.1	8 / 0	2026-01-20
2.4.0	8 / 0	2026-01-12
2.3.0	8 / 0	2025-12-15
2.2.2	8 / 0	2025-12-08
2.2.1	8 / 0	2025-10-15
2.2.0	8 / 0	2025-09-10
2.1.2	8 / 0	2025-08-07
2.1.1	8 / 0	2025-07-14
2.1.0	8 / 0	2025-05-27
2.0.0	8 / 0	2025-05-09

v2.5.19

1 finding

LOW No provenance attestation provenance

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

v2.5.18

1 finding

LOW No provenance attestation provenance

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

v2.5.17

1 finding

LOW No provenance attestation provenance

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

v2.5.15

1 finding

LOW No provenance attestation provenance

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

v2.5.14

1 finding

LOW No provenance attestation provenance

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

v2.5.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.5.11

1 finding

LOW No provenance attestation provenance

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

v2.5.10

1 finding

LOW No provenance attestation provenance

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

v2.5.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.5.8

1 finding

LOW No provenance attestation provenance

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

v2.5.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.5.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.5.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.5.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.5.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.5.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.5.1

1 finding

LOW No provenance attestation provenance

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

v2.5.0

1 finding

LOW No provenance attestation provenance

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

v2.4.13

1 finding

LOW No provenance attestation provenance

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

v2.4.12

1 finding

LOW No provenance attestation provenance

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

v2.4.11

1 finding

LOW No provenance attestation provenance

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

v2.4.10

1 finding

LOW No provenance attestation provenance

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

v2.4.9

1 finding

LOW No provenance attestation provenance

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

v2.4.8

1 finding

LOW No provenance attestation provenance

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

v2.4.7

1 finding

LOW No provenance attestation provenance

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

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. Consider requesting the maintainer enable provenance via CI/CD.

v2.4.3

1 finding

LOW No provenance attestation provenance

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

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

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.0

1 finding

LOW No provenance attestation provenance

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

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.2

1 finding

LOW No provenance attestation provenance

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

v2.2.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.2.0

1 finding

LOW No provenance attestation provenance

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

v2.1.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.1.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.1.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.0.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.