@mirohq/design-system-combobox
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-chip | AI (dependencies): Internal Miro design system sibling package; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-icons | AI (dependencies): Internal Miro design system sibling package; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-utils | AI (dependencies): Internal Miro design system sibling package; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-id | AI (dependencies): Internal Miro design system sibling package; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-stitches | AI (dependencies): Internal Miro design system sibling package; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-form | AI (dependencies): Internal Miro design system sibling package; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-primitive | AI (dependencies): Internal Miro design system sibling package; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-input | AI (dependencies): Internal Miro design system sibling package; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-select | AI (dependencies): Internal Miro design system sibling package; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-scroll-area | AI (dependencies): Internal Miro design system sibling package; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-tooltip | AI (dependencies): Internal Miro design system sibling package; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-previous | AI (dependencies): Internal Miro design system sibling package; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-aria-disabled | AI (dependencies): Internal Miro design system sibling package; not a third-party risk. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-layout-effect | AI (dependencies): Internal Miro design system sibling package; not a third-party risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Miro DS packages consistently lack description/repo/keywords; structural pattern, not spam. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across Miro design system monorepo packages; not a spam indicator here. | ai |
Versions (showing 52 of 52)
| Version | Deps | Published |
|---|---|---|
| 1.5.22 | 19 / 0 | |
| 1.5.21 | 19 / 0 | |
| 1.5.20 | 19 / 0 | |
| 1.5.19 | 19 / 0 | |
| 1.5.18 | 19 / 0 | |
| 1.5.17 | 19 / 0 | |
| 1.5.16 | 19 / 0 | |
| 1.5.15 | 19 / 0 | |
| 1.5.14 | 19 / 0 | |
| 1.5.13 | 19 / 0 | |
| 1.4.32 | 19 / 0 | |
| 1.3.10 | 19 / 0 | |
| 1.3.9 | 19 / 0 | |
| 1.3.8 | 19 / 0 | |
| 1.3.7 | 19 / 0 | |
| 1.3.6 | 19 / 0 | |
| 1.3.5 | 19 / 0 | |
| 1.3.4 | 19 / 0 | |
| 1.3.3 | 19 / 0 | |
| 1.3.2 | 19 / 0 | |
| 1.3.1 | 19 / 0 | |
| 1.3.0 | 19 / 0 | |
| 1.2.4 | 18 / 0 | |
| 1.2.3 | 18 / 0 | |
| 1.2.2 | 18 / 0 | |
| 1.2.1 | 18 / 0 | |
| 1.2.0 | 18 / 0 | |
| 1.1.14 | 18 / 0 | |
| 1.1.13 | 18 / 0 | |
| 1.1.12 | 18 / 0 | |
| 1.1.11 | 18 / 0 | |
| 1.1.10 | 18 / 0 | |
| 1.1.9 | 18 / 0 | |
| 1.1.8 | 18 / 0 | |
| 1.1.7 | 18 / 0 | |
| 1.1.6 | 18 / 0 | |
| 1.1.5 | 18 / 0 | |
| 1.1.4 | 18 / 0 | |
| 1.1.3 | 18 / 0 | |
| 1.1.2 | 18 / 0 | |
| 1.1.1 | 18 / 0 | |
| 1.1.0 | 18 / 0 | |
| 1.0.9 | 18 / 0 | |
| 1.0.8 | 18 / 0 | |
| 1.0.7 | 18 / 0 | |
| 1.0.6 | 18 / 0 | |
| 1.0.5 | 18 / 0 | |
| 1.0.4 | 18 / 0 | |
| 1.0.3 | 18 / 0 | |
| 1.0.2 | 18 / 0 | |
| 1.0.1 | 18 / 0 | |
| 1.0.0 | 18 / 0 |
v1.5.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.