@mirohq/design-system
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:@mirohq/design-system-use-aria-disabled | AI (dependencies): First-party Miro design system sub-package; same publisher/monorepo as parent. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-local-storage | AI (dependencies): First-party Miro design system sub-package; same publisher/monorepo as parent. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-tag | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-flex | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-grid | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-badge | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-types | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-utils | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-button | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-slider | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-styles | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-box | AI (dependencies): First-party Miro design system sub-package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-press | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-typography | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-logger | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-switch | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-spinner | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-toolbar | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-tooltip | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-calendar | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-stitches | AI (dependencies): First-party Miro design system sub-package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-textarea | AI (dependencies): First-party Miro design system sub-package. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Miro monorepo umbrella package; missing metadata is expected for org-internal packages. | ai | |
| provenance | no-provenance | AI (provenance): Miro org packages consistently lack provenance; not a risk signal for this publisher. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established Miro design system package; empty description is a known pattern for this monorepo. | ai |
Versions (showing 51 of 73)
| Version | Deps | Published |
|---|---|---|
| 1.3.1 | 55 / 0 | |
| 1.3.0 | 55 / 0 | |
| 1.2.70 | 55 / 0 | |
| 1.2.69 | 55 / 0 | |
| 1.2.68 | 55 / 0 | |
| 1.2.67 | 55 / 0 | |
| 1.2.65 | 55 / 0 | |
| 1.2.63 | 55 / 0 | |
| 1.2.62 | 55 / 0 | |
| 1.2.60 | 55 / 0 | |
| 1.2.58 | 55 / 0 | |
| 1.2.53 | 55 / 0 | |
| 1.2.52 | 55 / 0 | |
| 1.2.51 | 55 / 0 | |
| 1.2.49 | 55 / 0 | |
| 1.2.48 | 55 / 0 | |
| 1.2.43 | 55 / 0 | |
| 1.2.42 | 55 / 0 | |
| 1.2.41 | 55 / 0 | |
| 1.2.40 | 55 / 0 | |
| 1.2.39 | 55 / 0 | |
| 1.2.38 | 55 / 0 | |
| 1.2.37 | 55 / 0 | |
| 1.2.33 | 55 / 0 | |
| 1.2.32 | 55 / 0 | |
| 1.2.26 | 55 / 0 | |
| 1.2.24 | 55 / 0 | |
| 1.2.22 | 55 / 0 | |
| 1.2.20 | 55 / 0 | |
| 1.2.19 | 55 / 0 | |
| 1.2.18 | 55 / 0 | |
| 1.2.16 | 55 / 0 | |
| 1.2.14 | 55 / 0 | |
| 1.2.13 | 55 / 0 | |
| 1.2.12 | 55 / 0 | |
| 1.2.11 | 55 / 0 | |
| 1.2.10 | 55 / 0 | |
| 1.2.6 | 55 / 0 | |
| 1.2.4 | 55 / 0 | |
| 1.2.3 | 55 / 0 | |
| 1.2.2 | 55 / 0 | |
| 1.2.0 | 55 / 0 | |
| 1.1.27 | 55 / 0 | |
| 1.1.25 | 55 / 0 | |
| 1.1.24 | 55 / 0 | |
| 1.1.20 | 55 / 0 | |
| 1.1.17 | 55 / 0 | |
| 1.1.16 | 55 / 0 | |
| 1.1.15 | 55 / 0 | |
| 1.1.12 | 55 / 0 | |
| 1.1.11 | 55 / 0 |
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.70
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.69
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.68
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.63
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.53
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.48
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.43
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.39
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.38
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.