@getpara/core-components
Capsule Core Components
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established package with 149 versions; lack of Sigstore attestation is consistent across all prior releases. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 3.8.0 | 6 / 24 | |
| 3.7.0 | 6 / 24 | |
| 3.6.0 | 6 / 24 | |
| 3.5.1 | 6 / 24 | |
| 3.5.0 | 6 / 24 | |
| 3.4.0 | 6 / 24 | |
| 3.3.0 | 6 / 24 | |
| 3.2.0 | 6 / 24 | |
| 3.1.0 | 6 / 24 | |
| 3.0.0 | 6 / 24 | |
| 2.32.1 | 6 / 24 | |
| 2.32.0 | 6 / 24 | |
| 2.31.0 | 6 / 24 | |
| 2.28.0 | 6 / 24 | |
| 2.27.0 | 6 / 24 | |
| 2.26.0 | 6 / 24 | |
| 2.25.0 | 6 / 24 | |
| 2.24.0 | 6 / 24 | |
| 2.22.0 | 6 / 24 | |
| 2.21.0 | 6 / 24 | |
| 2.20.0 | 6 / 24 | |
| 2.5.0 | 6 / 24 | |
| 2.4.0 | 6 / 24 | |
| 2.3.0 | 6 / 24 | |
| 2.2.0 | 6 / 24 | |
| 2.1.0 | 6 / 24 | |
| 2.0.0 | 6 / 24 |
v3.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nsquare) than the most recent previously approved version (kwi25) on 2026-01-16, but nsquare 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.
v2.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (kwi25) than the most recent previously approved version (nsquare) on 2025-12-30, but kwi25 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.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.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.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.