@pega/cosmos-react-work
Supply chain provenance
Status for the latest visible version.
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
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): Private enterprise SDK from Pegasystems; no public repo/description is expected for internal component libraries. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent across all versions of this Pegasystems component library; not a malware indicator. | ai | |
| provenance | no-provenance | AI (provenance): No provenance across all 1279 versions; stable pattern for this publisher. | ai | |
| phantom-deps | phantom-dep:@types/react | AI (phantom-deps): @types packages declared as runtime deps by convention in this TypeScript component library. | ai | |
| phantom-deps | phantom-dep:@types/react-dom | AI (phantom-deps): @types packages declared as runtime deps by convention in this TypeScript component library. | ai | |
| phantom-deps | phantom-dep:@types/styled-components | AI (phantom-deps): @types packages declared as runtime deps by convention in this TypeScript component library. | ai |
Versions (showing 51 of 67)
| Version | Deps | Published |
|---|---|---|
| 8.21.7 | 9 / 7 | |
| 8.21.6 | 9 / 7 | |
| 8.21.5 | 9 / 7 | |
| 8.21.4 | 9 / 7 | |
| 8.21.3 | 9 / 7 | |
| 8.21.2 | 9 / 7 | |
| 8.21.1 | 9 / 7 | |
| 8.21.0 | 9 / 7 | |
| 8.20.0 | 9 / 7 | |
| 8.19.0 | 9 / 7 | |
| 8.18.3 | 9 / 7 | |
| 8.18.2 | 9 / 7 | |
| 8.18.1 | 9 / 7 | |
| 8.18.0 | 9 / 7 | |
| 8.17.2 | 9 / 7 | |
| 8.17.1 | 9 / 7 | |
| 8.17.0 | 9 / 7 | |
| 8.16.1 | 9 / 7 | |
| 8.16.0 | 9 / 7 | |
| 8.15.5 | 9 / 7 | |
| 8.15.4 | 9 / 7 | |
| 8.15.3 | 9 / 7 | |
| 8.15.2 | 9 / 7 | |
| 8.15.1 | 9 / 7 | |
| 8.15.0 | 9 / 7 | |
| 8.14.0 | 9 / 7 | |
| 8.13.1 | 9 / 7 | |
| 8.13.0 | 9 / 7 | |
| 8.12.1 | 9 / 7 | |
| 8.12.0 | 9 / 7 | |
| 8.11.0 | 9 / 7 | |
| 8.10.0 | 9 / 7 | |
| 8.9.5 | 9 / 7 | |
| 8.9.4 | 9 / 7 | |
| 8.9.3 | 9 / 7 | |
| 8.9.2 | 9 / 7 | |
| 8.9.1 | 9 / 7 | |
| 8.9.0 | 9 / 7 | |
| 8.8.1 | 9 / 7 | |
| 8.8.0 | 9 / 7 | |
| 7.17.0 | 9 / 7 | |
| 7.16.5 | 9 / 7 | |
| 7.16.4 | 9 / 7 | |
| 7.16.3 | 9 / 7 | |
| 7.16.2 | 9 / 7 | |
| 7.16.1 | 9 / 7 | |
| 7.16.0 | 9 / 7 | |
| 7.15.0 | 9 / 7 | |
| 7.14.1 | 9 / 7 | |
| 7.14.0 | 9 / 7 | |
| 7.13.0 | 9 / 7 |
v8.21.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.15.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.17.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.