← Home

@mirohq/design-system-icons

## Adding a new Icon

94
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.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): ivanbanov.miro is a Miro org publisher with strong approval track record; transition appears legitimate. ai
dependencies unvetted-dep:@mirohq/design-system-utils AI (dependencies): Internal Miro org scoped package; consistent with design-system monorepo pattern. ai
dependencies unvetted-dep:@mirohq/design-system-stitches AI (dependencies): Internal Miro org scoped package; consistent with design-system monorepo pattern. ai
dependencies unvetted-dep:@mirohq/design-system-use-local-storage AI (dependencies): Internal Miro org scoped package; consistent with design-system monorepo pattern. ai
provenance no-provenance AI (provenance): Miro org package with long history; no provenance is consistent across all versions. ai

Versions (showing 94 of 94)

Version Deps Published
1.45.0 5 / 10
1.44.1 5 / 10
1.44.0 5 / 10
1.43.1 5 / 10
1.43.0 5 / 10
1.42.0 5 / 10
1.41.0 5 / 10
1.40.2 5 / 10
1.40.1 5 / 10
1.40.0 5 / 10
1.39.2 5 / 10
1.39.1 5 / 10
1.39.0 5 / 10
1.38.2 5 / 10
1.38.1 5 / 10
1.38.0 5 / 10
1.37.5 5 / 10
1.37.4 5 / 10
1.37.3 5 / 10
1.37.2 5 / 10
1.37.1 5 / 10
1.37.0 5 / 10
1.36.5 5 / 10
1.36.4 5 / 10
1.36.3 5 / 10
1.36.2 5 / 10
1.36.1 5 / 10
1.36.0 5 / 10
1.35.15 5 / 10
1.35.14 5 / 10
1.35.13 5 / 10
1.35.12 5 / 10
1.35.11 5 / 10
1.35.10 5 / 10
1.35.9 5 / 10
1.35.8 5 / 10
1.35.7 5 / 10
1.35.6 5 / 10
1.35.5 5 / 10
1.35.4 5 / 10
1.35.3 5 / 10
1.35.2 5 / 10
1.35.1 5 / 10
1.35.0 5 / 10
1.34.3 5 / 10
1.34.2 5 / 10
1.34.1 5 / 10
1.34.0 5 / 10
1.33.1 5 / 10
1.33.0 5 / 10
1.32.0 5 / 10
1.31.0 5 / 10
1.30.1 5 / 10
1.30.0 5 / 10
1.29.0 5 / 10
1.28.0 5 / 10
1.27.1 5 / 10
1.27.0 5 / 10
1.26.1 5 / 10
1.26.0 5 / 10
1.25.0 5 / 10
1.24.0 5 / 10
1.23.0 5 / 10
1.22.0 5 / 10
1.21.0 5 / 10
1.20.2 5 / 10
1.20.1 5 / 10
1.20.0 5 / 10
1.19.1 5 / 10
1.19.0 5 / 10
1.18.0 5 / 10
1.17.0 5 / 10
1.16.0 5 / 10
1.15.0 5 / 10
1.14.0 5 / 10
1.13.0 5 / 10
1.12.0 5 / 10
1.11.1 5 / 10
1.11.0 5 / 10
1.10.2 5 / 10
1.10.1 5 / 10
1.10.0 5 / 10
1.9.0 5 / 10
1.8.0 5 / 10
1.7.1 5 / 10
1.7.0 5 / 10
1.6.2 5 / 10
1.6.1 5 / 10
1.6.0 5 / 10
1.5.0 5 / 10
1.4.0 5 / 10
1.3.0 5 / 10
1.2.0 5 / 10
1.0.0 5 / 10

v1.45.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.44.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.44.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.43.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.43.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.42.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.41.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.35.10

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.35.9

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.35.8

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.35.7

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.35.6

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.35.5

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.35.4

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.35.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.35.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.35.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.35.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.34.3

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.34.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.34.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.34.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.33.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.33.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.32.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.31.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.30.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.30.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.29.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.28.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.27.1

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.27.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.26.1

2 findings
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: mirohq-admin → ivanbanov.miro (on 2025-12-11, known maintainer) provenance

This version was published by a different npm account (ivanbanov.miro) than the most recent previously approved version (mirohq-admin) on 2025-12-11, but ivanbanov.miro is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.26.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.25.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.24.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.23.0

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.