@pega/cosmos-react-condition-builder

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

Maintainers

bob-difronzocpmotionssowersbyricmarspega-cosmos

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): Corporate monorepo component; missing description is a stable pattern across all Pega Cosmos packages.	ai	2026/05/26
bogus-package	bogus-package	AI (bogus-package): Metadata signals are a stable false positive for this corporate component package with no public repo/homepage.	ai	2026/05/26
provenance	no-provenance	AI (provenance): Pega Cosmos packages consistently lack Sigstore provenance; stable pattern across 1280 versions.	ai	2026/05/26
phantom-deps	phantom-dep:@types/react-dom	AI (phantom-deps): Type declaration package; loaded by convention, not directly imported.	ai	2026/05/01
phantom-deps	phantom-dep:polished	AI (phantom-deps): Declared runtime dep used transitively; phantom-dep heuristic fires but not a real concern for this package.	ai	2026/05/01
phantom-deps	phantom-dep:@types/styled-components	AI (phantom-deps): Type declaration package; loaded by convention, not directly imported.	ai	2026/05/01
phantom-deps	phantom-dep:react-dom	AI (phantom-deps): Peer dependency declared by convention; framework-scoped, not a phantom dep concern.	ai	2026/05/01
phantom-deps	phantom-dep:@types/react	AI (phantom-deps): Type declaration package; loaded by convention, not directly imported.	ai	2026/05/01

Versions (showing 51 of 67)

View all versions

Version	Deps	Published
8.21.7	9 / 4	2026-05-26
8.21.6	9 / 4	2026-05-22
8.21.5	9 / 4	2026-05-19
8.21.4	9 / 4	2026-05-15
8.21.3	9 / 4	2026-05-14
8.21.2	9 / 4	2026-05-13
8.21.1	9 / 4	2026-05-05
8.21.0	9 / 4	2026-04-30
8.20.0	9 / 4	2026-04-30
8.19.0	9 / 4	2026-04-28
8.18.3	9 / 4	2026-04-27
8.18.2	9 / 4	2026-04-27
8.18.1	9 / 4	2026-04-23
8.18.0	9 / 4	2026-04-22
8.17.2	9 / 4	2026-04-20
8.17.1	9 / 4	2026-04-16
8.17.0	9 / 4	2026-04-10
8.16.1	9 / 4	2026-04-08
8.16.0	9 / 4	2026-04-02
8.15.5	9 / 4	2026-03-26
8.15.4	9 / 4	2026-03-25
8.15.3	9 / 4	2026-03-18
8.15.2	9 / 4	2026-03-11
8.15.1	9 / 4	2026-02-18
8.15.0	9 / 4	2026-02-06
8.14.0	9 / 4	2026-02-05
8.13.1	9 / 4	2026-01-28
8.13.0	9 / 4	2026-01-23
8.12.1	9 / 4	2026-01-21
8.12.0	9 / 4	2026-01-12
8.11.0	9 / 4	2025-12-23
8.10.0	9 / 4	2025-12-12
8.9.5	9 / 4	2025-12-04
8.9.4	9 / 4	2025-11-28
8.9.3	9 / 4	2025-11-21
8.9.2	9 / 4	2025-11-21
8.9.1	9 / 4	2025-11-20
8.9.0	9 / 4	2025-11-19
8.8.1	9 / 4	2025-11-17
8.8.0	9 / 4	2025-10-30
7.17.0	9 / 4	2026-06-04
7.16.5	9 / 4	2026-05-29
7.16.4	9 / 4	2026-05-27
7.16.3	9 / 4	2026-05-22
7.16.2	9 / 4	2026-05-22
7.16.1	9 / 4	2026-05-14
7.16.0	9 / 4	2026-05-08
7.15.0	9 / 4	2026-03-23
7.14.1	9 / 4	2026-03-09
7.14.0	9 / 4	2026-02-27
7.13.0	9 / 4	2026-02-21

v8.21.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.

v8.21.6

1 finding

LOW No provenance attestation provenance

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

v8.21.5

1 finding

LOW No provenance attestation provenance

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

v8.21.4

1 finding

LOW No provenance attestation provenance

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

v8.21.3

1 finding

LOW No provenance attestation provenance

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

v8.21.2

1 finding

LOW No provenance attestation provenance

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

v8.21.1

1 finding

LOW No provenance attestation provenance

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

v8.21.0

1 finding

LOW No provenance attestation provenance

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

v8.20.0

1 finding

LOW No provenance attestation provenance

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

v8.19.0

1 finding

LOW No provenance attestation provenance

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

v8.18.3

1 finding

LOW No provenance attestation provenance

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

v8.18.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.

v8.18.1

1 finding

LOW No provenance attestation provenance

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

v8.18.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.

v8.17.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.

v8.17.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.

v8.17.0

1 finding

LOW No provenance attestation provenance

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

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

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

v8.15.5

1 finding

LOW No provenance attestation provenance

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

v8.15.4

1 finding

LOW No provenance attestation provenance

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

v8.15.3

1 finding

LOW No provenance attestation provenance

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

v8.15.2

1 finding

LOW No provenance attestation provenance

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

v8.15.1

1 finding

LOW No provenance attestation provenance

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

v8.15.0

1 finding

LOW No provenance attestation provenance

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

v8.14.0

1 finding

LOW No provenance attestation provenance

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

v8.13.1

1 finding

LOW No provenance attestation provenance

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

v8.13.0

1 finding

LOW No provenance attestation provenance

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

v8.12.1

1 finding

LOW No provenance attestation provenance

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

v8.12.0

1 finding

LOW No provenance attestation provenance

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

v8.11.0

1 finding

LOW No provenance attestation provenance

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

v8.10.0

1 finding

LOW No provenance attestation provenance

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

v8.9.5

1 finding

LOW No provenance attestation provenance

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

v8.9.4

1 finding

LOW No provenance attestation provenance

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

v8.9.3

1 finding

LOW No provenance attestation provenance

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

v8.9.2

1 finding

LOW No provenance attestation provenance

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

v8.9.1

1 finding

LOW No provenance attestation provenance

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

v8.9.0

1 finding

LOW No provenance attestation provenance

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

v8.8.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.

v8.8.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.

v7.17.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.

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

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

v7.16.3

1 finding

LOW No provenance attestation provenance

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

v7.16.2

1 finding

LOW No provenance attestation provenance

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

v7.16.1

1 finding

LOW No provenance attestation provenance

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

v7.16.0

1 finding

LOW No provenance attestation provenance

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

v7.15.0

1 finding

LOW No provenance attestation provenance

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

v7.14.1

1 finding

LOW No provenance attestation provenance

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

v7.14.0

1 finding

LOW No provenance attestation provenance

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

v7.13.0

1 finding

LOW No provenance attestation provenance

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