@mirohq/design-system-styles
39
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
No source commit
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
ivanbanov.mirokaren.nmirohq-admin
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal Miro design-system package; missing metadata is typical for private/scoped monorepo packages, not a spam indicator. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Scoped internal package; missing description is consistent across this package family. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common; no other risk signals elevate this. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 3.2.32 | 1 / 0 | |
| 3.2.31 | 1 / 0 | |
| 3.2.30 | 1 / 0 | |
| 3.2.29 | 1 / 0 | |
| 3.2.28 | 1 / 0 | |
| 3.2.27 | 1 / 0 | |
| 3.2.26 | 1 / 0 | |
| 3.2.25 | 1 / 0 | |
| 3.2.24 | 1 / 0 | |
| 3.2.23 | 1 / 0 | |
| 3.2.22 | 1 / 0 | |
| 3.2.21 | 1 / 0 | |
| 3.2.20 | 1 / 0 | |
| 3.2.19 | 1 / 0 | |
| 3.2.18 | 1 / 0 | |
| 3.2.17 | 1 / 0 | |
| 3.2.16 | 1 / 0 | |
| 3.2.15 | 1 / 0 | |
| 3.2.14 | 1 / 0 | |
| 3.2.13 | 1 / 0 | |
| 3.2.12 | 1 / 0 | |
| 3.2.11 | 1 / 0 | |
| 3.2.10 | 1 / 0 | |
| 3.2.9 | 1 / 0 | |
| 3.2.8 | 1 / 0 | |
| 3.2.7 | 1 / 0 | |
| 3.2.6 | 1 / 0 | |
| 3.2.5 | 1 / 0 | |
| 3.2.4 | 1 / 0 | |
| 3.2.3 | 1 / 0 | |
| 3.2.2 | 1 / 0 | |
| 3.2.1 | 1 / 0 | |
| 3.2.0 | 1 / 0 | |
| 3.1.3 | 1 / 0 | |
| 3.1.2 | 1 / 0 | |
| 3.1.1 | 1 / 0 | |
| 3.1.0 | 1 / 0 | |
| 3.0.1 | 1 / 0 | |
| 3.0.0 | 1 / 0 |
v3.2.32
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.31
1 finding
INFO
No provenance attestation
provenance
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.