@mirohq/design-system-slider
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 a verified Miro org publisher with 869 approved packages; transition from mirohq-admin is a routine internal handoff. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-utils | AI (dependencies): Sibling Miro design system monorepo package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-styles | AI (dependencies): Sibling Miro design system monorepo package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-stitches | AI (dependencies): Sibling Miro design system monorepo package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-aria-disabled | AI (dependencies): Sibling Miro design system monorepo package; stable false positive for this org. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-types | AI (dependencies): Sibling Miro design system monorepo package; stable false positive for this org. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the Miro design system suite; consistent with org publishing practices. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with other @mirohq/design-system-* packages; not a spam indicator here. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal design system component; sparse metadata is consistent across the entire @mirohq/design-system-* package family. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 1.2.33 | 8 / 0 | |
| 1.2.32 | 8 / 0 | |
| 1.2.31 | 8 / 0 | |
| 1.2.30 | 8 / 0 | |
| 1.2.29 | 8 / 0 | |
| 1.2.28 | 8 / 0 | |
| 1.2.27 | 8 / 0 | |
| 1.2.26 | 8 / 0 | |
| 1.2.25 | 8 / 0 | |
| 1.2.24 | 8 / 0 | |
| 1.2.23 | 8 / 0 | |
| 1.2.22 | 8 / 0 | |
| 1.2.21 | 8 / 0 | |
| 1.2.20 | 8 / 0 | |
| 1.2.19 | 8 / 0 | |
| 1.2.18 | 8 / 0 | |
| 1.2.17 | 8 / 0 | |
| 1.2.16 | 8 / 0 | |
| 1.2.15 | 8 / 0 | |
| 1.2.14 | 8 / 0 | |
| 1.2.13 | 8 / 0 | |
| 1.2.12 | 8 / 0 | |
| 1.2.11 | 8 / 0 | |
| 1.2.10 | 8 / 0 | |
| 1.2.9 | 8 / 0 | |
| 1.2.8 | 8 / 0 | |
| 1.2.7 | 8 / 0 | |
| 1.2.6 | 8 / 0 | |
| 1.2.5 | 8 / 0 | |
| 1.2.4 | 8 / 0 | |
| 1.2.3 | 8 / 0 | |
| 1.2.2 | 8 / 0 | |
| 1.2.1 | 8 / 0 | |
| 1.2.0 | 8 / 0 | |
| 1.1.3 | 8 / 0 | |
| 1.1.2 | 8 / 0 | |
| 1.1.1 | 8 / 0 | |
| 1.1.0 | 8 / 0 | |
| 1.0.3 | 8 / 0 | |
| 1.0.2 | 8 / 0 | |
| 1.0.1 | 8 / 0 | |
| 1.0.0 | 8 / 0 |
v1.2.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.30
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.27
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.25
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.23
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.21
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.17
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.15
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.7
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.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
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.3
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.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.