@mirohq/design-system-toolbar
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): @radix-ui/react-direction is a legitimate Radix UI package; addition is consistent with the toolbar's existing @radix-ui/react-toolbar dependency. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the Miro design-system family; not a risk differentiator for this package. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-stitches | AI (dependencies): Internal Miro design-system sibling package; stable org-internal dependency. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-icon | AI (dependencies): Internal Miro design-system sibling package; stable org-internal dependency. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-press | AI (dependencies): Internal Miro design-system sibling package; stable org-internal dependency. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-utils | AI (dependencies): Internal Miro design-system sibling package; stable org-internal dependency. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-aria-disabled | AI (dependencies): Internal Miro design-system sibling package; stable org-internal dependency. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-styles | AI (dependencies): Internal Miro design-system sibling package; stable org-internal dependency. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent pattern across @mirohq/design-system-* packages; not a spam indicator here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Miro internal design system package; sparse metadata is consistent across the entire @mirohq/design-system-* family. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 3.4.2 | 11 / 0 | |
| 3.4.1 | 11 / 0 | |
| 3.4.0 | 11 / 0 | |
| 3.3.26 | 11 / 0 | |
| 3.3.22 | 11 / 0 | |
| 3.3.20 | 11 / 0 | |
| 3.3.18 | 11 / 0 | |
| 3.3.15 | 11 / 0 | |
| 3.3.11 | 11 / 0 | |
| 3.3.8 | 11 / 0 | |
| 3.2.0 | 10 / 0 | |
| 3.1.2 | 10 / 0 | |
| 3.1.0 | 9 / 0 | |
| 3.0.2 | 9 / 0 | |
| 3.0.1 | 9 / 0 | |
| 3.0.0 | 9 / 0 |
v3.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.22
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.8
2 findingsThis version was published by a different npm account than previous versions on 2026-03-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
2 findingsThis version was published by a different npm account than previous versions on 2026-01-12. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.