@bpmn-io/form-js-carbon-styles No license 32 versions

@bpmn-io/form-js-carbon-styles

npm Repository Homepage

32

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

bpmn-io-adminnikkubarmacphilippfrommemaxtruskaiir-camundavsgoulartbarinaliev-camundajarekdanielakalekseymanetov

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): Org team rotation on well-known bpmn-io package, no behavioral change.	ai	2026/07/19
maintainer-change	maintainer-removed	AI (maintainer-change): Routine maintainer rotation, no takeover indicators.	ai	2026/07/19
publish-pattern	dormant-publish	AI (publish-pattern): Monorepo package with irregular release cadence; no other risk indicators.	ai	2026/07/19
bogus-package	bogus-package	AI (bogus-package): Legit bpmn-io org package; spam-publisher overlap is incidental, no actual spam indicators.	ai	2026/07/19

Versions (showing 32 of 32)

Version	Deps	Published
1.24.1	0 / 3	2026-07-27
1.24.0	0 / 3	2026-07-15
1.23.1	0 / 3	2026-07-10
1.23.0	0 / 3	2026-06-29
1.21.3	0 / 3	2026-04-18
1.21.2	0 / 3	2026-03-18
1.21.1	0 / 3	2026-03-18
1.21.0	0 / 3	2026-03-12
1.20.1	0 / 3	2026-03-05
1.20.0	0 / 3	2026-03-04
1.19.0	0 / 3	2026-02-06
1.18.0	0 / 3	2025-10-24
1.17.0	0 / 3	2025-08-20
1.16.0	0 / 3	2025-07-21
1.15.5	0 / 3	2026-03-05
1.15.4	0 / 3	2026-02-18
1.15.3	0 / 3	2025-06-13
1.15.2	0 / 3	2025-04-30
1.15.0	0 / 3	2025-03-19
1.14.0	0 / 3	2025-02-13
1.13.2	0 / 3	2024-12-20
1.13.1	0 / 3	2024-12-13
1.13.0	0 / 3	2024-12-12
1.12.0	0 / 3	2024-11-19
1.11.3	0 / 3	2024-10-30
1.11.2	0 / 3	2024-10-28
1.11.1	0 / 3	2024-10-24
1.11.0	0 / 3	2024-10-23
1.10.1	0 / 3	2024-09-13
1.10.0	0 / 3	2024-08-26
1.9.2	0 / 3	2024-08-26
1.9.1	0 / 3	2024-08-15

v1.24.1

1 finding

LOW No provenance attestation provenance

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

v1.24.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: barmac → nikku (on 2026-07-15, known maintainer) provenance

This version was published by a different npm account (nikku) than the most recent previously approved version (barmac) on 2026-07-15, but nikku 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.23.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.

v1.23.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.

v1.21.3

1 finding

LOW No provenance attestation provenance

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

v1.21.2

1 finding

LOW No provenance attestation provenance

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

v1.21.1

1 finding

LOW No provenance attestation provenance

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

v1.21.0

1 finding

LOW No provenance attestation provenance

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

v1.20.1

1 finding

LOW No provenance attestation provenance

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

v1.20.0

1 finding

LOW No provenance attestation provenance

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

v1.19.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.

v1.18.0

1 finding

LOW No provenance attestation provenance

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

v1.17.0

1 finding

LOW No provenance attestation provenance

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

v1.16.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.

v1.15.5

1 finding

LOW No provenance attestation provenance

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

v1.15.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.

v1.15.3

1 finding

LOW No provenance attestation provenance

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

v1.15.2

1 finding

LOW No provenance attestation provenance

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

v1.15.0

1 finding

LOW No provenance attestation provenance

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

v1.14.0

1 finding

LOW No provenance attestation provenance

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

v1.13.2

1 finding

LOW No provenance attestation provenance

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

v1.13.1

1 finding

LOW No provenance attestation provenance

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

v1.13.0

1 finding

LOW No provenance attestation provenance

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

v1.12.0

1 finding

LOW No provenance attestation provenance

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

v1.11.3

1 finding

LOW No provenance attestation provenance

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

v1.11.2

1 finding

LOW No provenance attestation provenance

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

v1.11.1

1 finding

LOW No provenance attestation provenance

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

v1.11.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: skaiir-camunda → vsgoulart (on 2024-10-23, known maintainer) provenance

This version was published by a different npm account (vsgoulart) than the most recent previously approved version (skaiir-camunda) on 2024-10-23, but vsgoulart 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.10.1

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: skaiir-camunda → vsgoulart (on 2024-09-13, known maintainer) provenance

This version was published by a different npm account (vsgoulart) than the most recent previously approved version (skaiir-camunda) on 2024-09-13, but vsgoulart 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.10.0

1 finding

LOW No provenance attestation provenance

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

v1.9.2

1 finding

LOW No provenance attestation provenance

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

v1.9.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.