@mirohq/design-system-base-input
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 with 530 approved packages; transition from mirohq-admin appears legitimate. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo component; empty description is consistent across all @mirohq/design-system-* packages. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across the @mirohq design system suite; not a risk indicator for this publisher. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-form | AI (dependencies): Internal Miro design system sibling package; stable false positive for this org's packages. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-icon | AI (dependencies): Internal Miro design system sibling package; stable false positive for this org's packages. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-primitive | AI (dependencies): Internal Miro design system sibling package; stable false positive for this org's packages. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-press | AI (dependencies): Internal Miro design system sibling package; stable false positive for this org's packages. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-utils | AI (dependencies): Internal Miro design system sibling package; stable false positive for this org's packages. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-aria-disabled | AI (dependencies): Internal Miro design system sibling package; stable false positive for this org's packages. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-layout-effect | AI (dependencies): Internal Miro design system sibling package; stable false positive for this org's packages. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established Miro internal design system package; missing metadata is org convention, not a spam indicator. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-button | AI (dependencies): Internal Miro design system sibling package; stable false positive for this org's packages. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-tooltip | AI (dependencies): Internal Miro design system sibling package; stable false positive for this org's packages. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-stitches | AI (dependencies): Internal Miro design system sibling package; stable false positive for this org's packages. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 1.3.38 | 13 / 0 | |
| 1.3.37 | 13 / 0 | |
| 1.3.36 | 13 / 0 | |
| 1.3.35 | 13 / 0 | |
| 1.3.34 | 13 / 0 | |
| 1.3.33 | 13 / 0 | |
| 1.3.32 | 13 / 0 | |
| 1.3.31 | 13 / 0 | |
| 1.3.30 | 13 / 0 | |
| 1.3.29 | 13 / 0 | |
| 1.3.28 | 13 / 0 | |
| 1.3.27 | 13 / 0 | |
| 1.3.26 | 13 / 0 | |
| 1.3.25 | 13 / 0 | |
| 1.3.24 | 13 / 0 | |
| 1.3.23 | 13 / 0 | |
| 1.3.22 | 13 / 0 | |
| 1.3.21 | 13 / 0 | |
| 1.3.20 | 13 / 0 | |
| 1.3.19 | 13 / 0 | |
| 1.3.18 | 13 / 0 | |
| 1.3.17 | 13 / 0 | |
| 1.3.16 | 13 / 0 | |
| 1.3.15 | 13 / 0 | |
| 1.3.14 | 13 / 0 | |
| 1.3.13 | 13 / 0 | |
| 1.3.12 | 13 / 0 | |
| 1.3.11 | 13 / 0 | |
| 1.3.10 | 13 / 0 | |
| 1.3.9 | 13 / 0 | |
| 1.3.8 | 13 / 0 | |
| 1.3.7 | 13 / 0 | |
| 1.3.6 | 13 / 0 | |
| 1.3.5 | 13 / 0 | |
| 1.3.4 | 13 / 0 | |
| 1.3.3 | 13 / 0 | |
| 1.3.2 | 13 / 0 | |
| 1.3.1 | 13 / 0 | |
| 1.3.0 | 13 / 0 | |
| 1.2.3 | 13 / 0 | |
| 1.2.2 | 13 / 0 | |
| 1.2.1 | 13 / 0 | |
| 1.2.0 | 13 / 0 | |
| 1.1.1 | 13 / 0 | |
| 1.1.0 | 13 / 0 | |
| 1.0.2 | 13 / 0 | |
| 1.0.1 | 13 / 0 | |
| 1.0.0 | 13 / 0 |
v1.3.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.33
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.29
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.20
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.3
2 findingsThis version was published by a different npm account than previous versions on 2025-12-29. 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.2.2
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2025-12-15. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This 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.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.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.
v1.1.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.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.
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.