@mirohq/design-system-flex No license 36 versions

@mirohq/design-system-flex

npm

36

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

ivanbanov.mirokaren.nmirohq-admin

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 account with 869 approved packages; transition appears legitimate.	ai	2026/05/21
dependencies	unvetted-dep:@mirohq/design-system-utils	AI (dependencies): Sibling Miro design-system monorepo package; stable internal dependency pattern across all versions.	ai	2026/05/17
dependencies	unvetted-dep:@mirohq/design-system-stitches	AI (dependencies): Sibling Miro design-system monorepo package; stable internal dependency pattern across all versions.	ai	2026/05/17
bogus-package	bogus-package	AI (bogus-package): Internal Miro design-system component; sparse metadata is consistent across the whole package family.	ai	2026/05/17
npm-metadata	no-description	AI (npm-metadata): Intentionally minimal metadata for internal Miro design-system packages; stable pattern.	ai	2026/05/17

Versions (showing 36 of 36)

Version	Deps	Published
3.2.29	3 / 0	2026-05-28
3.2.28	3 / 0	2026-05-11
3.2.27	3 / 0	2026-05-07
3.2.26	3 / 0	2026-05-07
3.2.25	3 / 0	2026-04-29
3.2.24	3 / 0	2026-04-29
3.2.23	3 / 0	2026-04-27
3.2.22	3 / 0	2026-04-23
3.2.21	3 / 0	2026-04-23
3.2.20	3 / 0	2026-04-22
3.2.19	3 / 0	2026-04-20
3.2.18	3 / 0	2026-04-16
3.2.17	3 / 0	2026-04-13
3.2.16	3 / 0	2026-04-10
3.2.15	3 / 0	2026-04-07
3.2.14	3 / 0	2026-04-02
3.2.13	3 / 0	2026-03-24
3.2.12	3 / 0	2026-03-23
3.2.11	3 / 0	2026-03-23
3.2.10	3 / 0	2026-03-20
3.2.9	3 / 0	2026-03-19
3.2.8	3 / 0	2026-03-18
3.2.7	3 / 0	2026-03-18
3.2.6	3 / 0	2026-03-18
3.2.5	3 / 0	2026-03-13
3.2.4	3 / 0	2026-03-10
3.2.3	3 / 0	2026-03-03
3.2.2	3 / 0	2026-03-02
3.2.1	3 / 0	2026-01-20
3.2.0	3 / 0	2026-01-12
3.1.2	3 / 0	2025-12-11
3.1.1	3 / 0	2025-10-15
3.1.0	3 / 0	2025-09-10
3.0.2	3 / 0	2025-08-07
3.0.1	3 / 0	2025-07-14
3.0.0	3 / 0	2025-05-09

v3.2.29

1 finding

LOW No provenance attestation provenance

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

v3.2.28

1 finding

LOW No provenance attestation provenance

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

v3.2.27

1 finding

LOW No provenance attestation provenance

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

v3.2.26

1 finding

LOW No provenance attestation provenance

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

v3.2.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.19

1 finding

LOW No provenance attestation provenance

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

v3.2.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.17

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.16

1 finding

LOW No provenance attestation provenance

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

v3.2.15

1 finding

LOW No provenance attestation provenance

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

v3.2.14

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.13

1 finding

LOW No provenance attestation provenance

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

v3.2.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.11

1 finding

LOW No provenance attestation provenance

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

v3.2.10

1 finding

LOW No provenance attestation provenance

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

v3.2.9

1 finding

LOW No provenance attestation provenance

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

v3.2.8

1 finding

LOW No provenance attestation provenance

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

v3.2.7

1 finding

LOW No provenance attestation provenance

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

v3.2.6

1 finding

LOW No provenance attestation provenance

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

v3.2.5

1 finding

LOW No provenance attestation provenance

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

v3.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.2.3

2 findings

HIGH Publisher changed: mirohq-admin → ivanbanov.miro (on 2026-03-03) provenance

This version was published by a different npm account than previous versions on 2026-03-03. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.2.2

2 findings

HIGH Publisher changed: mirohq-admin → ivanbanov.miro (on 2026-03-02) provenance

This version was published by a different npm account than previous versions on 2026-03-02. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.2.1

2 findings

HIGH Publisher changed: mirohq-admin → ivanbanov.miro (on 2026-01-20) provenance

This version was published by a different npm account than previous versions on 2026-01-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.2.0

2 findings

HIGH Publisher changed: mirohq-admin → ivanbanov.miro (on 2026-01-12) provenance

This version was published by a different npm account than previous versions on 2026-01-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v3.1.2

2 findings

HIGH Publisher changed: mirohq-admin → ivanbanov.miro (on 2025-12-11) provenance

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.

LOW No provenance attestation provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v3.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.