@cosmograph/react
Cosmograph React Wrapper
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 |
|---|---|---|---|---|
| license | uncommon-license:CC-BY-NC-4.0 | AI (license): CC-BY-NC-4.0 is a known license; non-commercial restriction is a legal concern, not a security risk. Stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established package (1000+ days, 63 versions); lack of provenance is common and not a risk signal here. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 2.3.2 | 1 / 0 | |
| 2.3.1 | 1 / 0 | |
| 2.3.0 | 1 / 0 | |
| 2.2.0 | 1 / 0 | |
| 2.1.0 | 1 / 0 | |
| 2.0.1 | 1 / 0 | |
| 2.0.0 | 1 / 0 |
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.