@mirohq/design-system-dropdown-menu
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 | publisher-changed | AI (provenance): ivanbanov.miro is an established Miro org publisher (869 approved); transition from mirohq-admin appears legitimate. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped internal design system package; empty description is consistent across the Miro DS monorepo. | ai | |
| provenance | no-provenance | AI (provenance): Miro design system packages consistently lack provenance; not a risk indicator for this publisher. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-icons | AI (dependencies): Sibling @mirohq/design-system-* dep; stable false positive for this monorepo package family. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-types | AI (dependencies): Sibling @mirohq/design-system-* dep; stable false positive for this monorepo package family. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-utils | AI (dependencies): Sibling @mirohq/design-system-* dep; stable false positive for this monorepo package family. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-styles | AI (dependencies): Sibling @mirohq/design-system-* dep; stable false positive for this monorepo package family. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-stitches | AI (dependencies): Sibling @mirohq/design-system-* dep; stable false positive for this monorepo package family. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-icon | AI (dependencies): Sibling @mirohq/design-system-* dep; stable false positive for this monorepo package family. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Miro design system package; missing metadata is expected for scoped monorepo components. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-hotkey | AI (dependencies): Sibling @mirohq/design-system-* dep; stable false positive for this monorepo package family. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-switch | AI (dependencies): Sibling @mirohq/design-system-* dep; stable false positive for this monorepo package family. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-scroll-area | AI (dependencies): Sibling @mirohq/design-system-* dep; stable false positive for this monorepo package family. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-tooltip | AI (dependencies): Sibling @mirohq/design-system-* dep; stable false positive for this monorepo package family. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-previous | AI (dependencies): Sibling @mirohq/design-system-* dep; stable false positive for this monorepo package family. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-aria-disabled | AI (dependencies): Sibling @mirohq/design-system-* dep; stable false positive for this monorepo package family. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-layout-effect | AI (dependencies): Sibling @mirohq/design-system-* dep; stable false positive for this monorepo package family. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-primitive | AI (dependencies): Sibling @mirohq/design-system-* dep; stable false positive for this monorepo package family. | ai |
Versions (showing 91 of 91)
| Version | Deps | Published |
|---|---|---|
| 5.4.36 | 15 / 0 | |
| 5.4.35 | 15 / 0 | |
| 5.4.34 | 15 / 0 | |
| 5.4.33 | 15 / 0 | |
| 5.4.32 | 15 / 0 | |
| 5.4.31 | 15 / 0 | |
| 5.4.30 | 15 / 0 | |
| 5.4.29 | 15 / 0 | |
| 5.4.28 | 15 / 0 | |
| 5.4.27 | 15 / 0 | |
| 5.4.26 | 15 / 0 | |
| 5.4.25 | 15 / 0 | |
| 5.4.24 | 15 / 0 | |
| 5.4.23 | 15 / 0 | |
| 5.4.22 | 15 / 0 | |
| 5.4.21 | 15 / 0 | |
| 5.4.20 | 15 / 0 | |
| 5.4.19 | 15 / 0 | |
| 5.4.18 | 15 / 0 | |
| 5.4.17 | 15 / 0 | |
| 5.4.16 | 15 / 0 | |
| 5.4.15 | 15 / 0 | |
| 5.4.14 | 15 / 0 | |
| 5.4.13 | 15 / 0 | |
| 5.4.12 | 15 / 0 | |
| 5.4.11 | 15 / 0 | |
| 5.4.10 | 15 / 0 | |
| 5.4.9 | 15 / 0 | |
| 5.4.8 | 15 / 0 | |
| 5.4.7 | 15 / 0 | |
| 5.4.6 | 15 / 0 | |
| 5.4.5 | 15 / 0 | |
| 5.4.4 | 15 / 0 | |
| 5.4.3 | 15 / 0 | |
| 5.4.2 | 15 / 0 | |
| 5.4.1 | 15 / 0 | |
| 5.4.0 | 15 / 0 | |
| 5.3.12 | 15 / 0 | |
| 5.3.11 | 15 / 0 | |
| 5.3.10 | 15 / 0 | |
| 5.3.9 | 15 / 0 | |
| 5.3.8 | 15 / 0 | |
| 5.3.7 | 15 / 0 | |
| 5.3.6 | 15 / 0 | |
| 5.3.5 | 15 / 0 | |
| 5.3.4 | 15 / 0 | |
| 5.3.3 | 15 / 0 | |
| 5.3.2 | 15 / 0 | |
| 5.3.1 | 15 / 0 | |
| 5.3.0 | 15 / 0 | |
| 5.2.1 | 15 / 0 | |
| 5.2.0 | 15 / 0 | |
| 5.1.14 | 15 / 0 | |
| 5.1.13 | 15 / 0 | |
| 5.1.12 | 15 / 0 | |
| 5.1.11 | 15 / 0 | |
| 5.1.10 | 15 / 0 | |
| 5.1.9 | 15 / 0 | |
| 5.1.8 | 15 / 0 | |
| 5.1.7 | 15 / 0 | |
| 5.1.6 | 15 / 0 | |
| 5.1.5 | 15 / 0 | |
| 5.1.4 | 15 / 0 | |
| 5.1.3 | 15 / 0 | |
| 5.1.2 | 15 / 0 | |
| 5.1.1 | 15 / 0 | |
| 5.1.0 | 15 / 0 | |
| 5.0.23 | 15 / 0 | |
| 5.0.22 | 15 / 0 | |
| 5.0.21 | 15 / 0 | |
| 5.0.20 | 15 / 0 | |
| 5.0.19 | 15 / 0 | |
| 5.0.18 | 15 / 0 | |
| 5.0.17 | 15 / 0 | |
| 5.0.16 | 15 / 0 | |
| 5.0.15 | 15 / 0 | |
| 5.0.14 | 15 / 0 | |
| 5.0.13 | 15 / 0 | |
| 5.0.12 | 15 / 0 | |
| 5.0.11 | 15 / 0 | |
| 5.0.10 | 16 / 0 | |
| 5.0.9 | 16 / 0 | |
| 5.0.8 | 16 / 0 | |
| 5.0.7 | 16 / 0 | |
| 5.0.6 | 16 / 0 | |
| 5.0.5 | 16 / 0 | |
| 5.0.4 | 16 / 0 | |
| 5.0.3 | 16 / 0 | |
| 5.0.2 | 16 / 0 | |
| 5.0.1 | 16 / 0 | |
| 5.0.0 | 16 / 0 |
v5.4.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.4.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.3.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.
v5.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.2.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.
v5.1.14
2 findingsThis version was published by a different npm account than previous versions on 2025-12-11. 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.
v5.1.13
2 findingsThis version was published by a different npm account than previous versions on 2025-12-11. 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.
v5.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.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.
v5.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.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.