@mirohq/design-system-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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Scoped Miro package; empty description is metadata gap, not malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): Provenance absence is infrastructure gap; 930-day history and stable versioning mitigate risk. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-form | AI (dependencies): Internal Miro design system sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-use-press | AI (dependencies): Internal Miro design system sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-icons | AI (dependencies): Internal Miro design system sibling package; stable pattern across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Monorepo component packages commonly lack description/repo/keywords; not indicative of spam. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-base-input | AI (dependencies): Internal Miro design system sibling package; stable pattern across all versions. | ai | |
| dependencies | unvetted-dep:@mirohq/design-system-utils | AI (dependencies): Internal Miro design system sibling package; stable pattern across all versions. | ai |
Versions (showing 51 of 63)
| Version | Deps | Published |
|---|---|---|
| 1.5.7 | 5 / 0 | |
| 1.5.6 | 5 / 0 | |
| 1.5.5 | 5 / 0 | |
| 1.5.4 | 5 / 0 | |
| 1.5.3 | 5 / 0 | |
| 1.5.2 | 5 / 0 | |
| 1.5.1 | 5 / 0 | |
| 1.5.0 | 5 / 0 | |
| 1.4.44 | 5 / 0 | |
| 1.4.43 | 5 / 0 | |
| 1.4.42 | 5 / 0 | |
| 1.4.41 | 5 / 0 | |
| 1.4.40 | 5 / 0 | |
| 1.4.39 | 5 / 0 | |
| 1.4.38 | 5 / 0 | |
| 1.4.37 | 5 / 0 | |
| 1.4.36 | 5 / 0 | |
| 1.4.35 | 5 / 0 | |
| 1.4.34 | 5 / 0 | |
| 1.4.33 | 5 / 0 | |
| 1.4.32 | 5 / 0 | |
| 1.4.31 | 5 / 0 | |
| 1.4.30 | 5 / 0 | |
| 1.3.1 | 5 / 0 | |
| 1.3.0 | 5 / 0 | |
| 1.2.11 | 5 / 0 | |
| 1.2.10 | 5 / 0 | |
| 1.2.9 | 5 / 0 | |
| 1.2.8 | 5 / 0 | |
| 1.2.7 | 5 / 0 | |
| 1.2.6 | 5 / 0 | |
| 1.2.5 | 5 / 0 | |
| 1.2.4 | 5 / 0 | |
| 1.2.3 | 5 / 0 | |
| 1.2.2 | 5 / 0 | |
| 1.2.1 | 5 / 0 | |
| 1.2.0 | 5 / 0 | |
| 1.1.16 | 5 / 0 | |
| 1.1.15 | 5 / 0 | |
| 1.1.14 | 5 / 0 | |
| 1.1.13 | 5 / 0 | |
| 1.1.12 | 5 / 0 | |
| 1.1.11 | 5 / 0 | |
| 1.1.10 | 5 / 0 | |
| 1.1.9 | 5 / 0 | |
| 1.1.8 | 5 / 0 | |
| 1.1.7 | 5 / 0 | |
| 1.1.6 | 5 / 0 | |
| 1.1.5 | 5 / 0 | |
| 1.1.4 | 5 / 0 | |
| 1.1.3 | 5 / 0 |
v1.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.44
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.42
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.41
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.40
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.38
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.37
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.36
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.35
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.34
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.33
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.32
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.31
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.30
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.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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.