@kapaai/react-sdk
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@kapaai/utils | AI (phantom-deps): Same-org sibling dep; bundled SDK may not show direct imports at package level — stable false positive. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all versions of this package; absence of provenance is common and not a risk indicator here. | ai | |
| dependencies | unvetted-dep:@hcaptcha/react-hcaptcha | AI (dependencies): Legitimate CAPTCHA library; expected dependency for an AI chat widget SDK. | ai | |
| dependencies | unvetted-dep:@fingerprintjs/fingerprintjs-pro-spa | AI (dependencies): Legitimate fingerprinting library; expected for bot/spam protection in this SDK. | ai | |
| dependencies | unvetted-dep:@fingerprintjs/fingerprintjs-pro-react | AI (dependencies): Legitimate fingerprinting React wrapper; expected for bot/spam protection in this SDK. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 0.9.10 | 5 / 14 | |
| 0.9.9 | 5 / 14 | |
| 0.9.8 | 5 / 14 | |
| 0.9.7 | 5 / 14 | |
| 0.9.5 | 6 / 13 | |
| 0.9.4 | 6 / 14 | |
| 0.9.3 | 6 / 14 | |
| 0.9.2 | 5 / 12 | |
| 0.9.1 | 5 / 12 | |
| 0.9.0 | 5 / 12 | |
| 0.8.0 | 5 / 12 | |
| 0.7.0 | 5 / 12 | |
| 0.6.0 | 5 / 12 | |
| 0.5.1 | 5 / 12 | |
| 0.5.0 | 5 / 12 | |
| 0.4.2 | 5 / 12 | |
| 0.4.1 | 5 / 12 | |
| 0.4.0 | 5 / 12 | |
| 0.3.0 | 5 / 12 | |
| 0.2.0 | 5 / 12 | |
| 0.1.4 | 5 / 12 | |
| 0.1.3 | 5 / 12 | |
| 0.1.2 | 5 / 12 | |
| 0.1.1 | 5 / 12 | |
| 0.1.0 | 5 / 12 | |
| 0.0.5 | 3 / 11 | |
| 0.0.4 | 2 / 11 | |
| 0.0.3 | 2 / 11 |
v0.9.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.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.
v0.9.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.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.
v0.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.
v0.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.