@nexus-cross/connect-kit-react
React components and hooks for @nexus-cross/connect-kit wallet connection
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@nexus-cross/kyc | AI (dependencies): Same-org monorepo sibling versioned in lockstep, not a third-party dep. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): Internal org package addition, consistent with monorepo pattern. | ai | |
| phantom-deps | phantom-dep:@nexus-cross/crossx-design-system | AI (phantom-deps): Same-org scope re-export pattern common in component libraries. | ai | |
| provenance | no-provenance | AI (provenance): New package without provenance is common; no other risk signals present. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 1.3.4 | 6 / 9 | |
| 1.3.3 | 5 / 9 | |
| 1.3.2 | 5 / 9 | |
| 1.3.1 | 5 / 9 | |
| 1.3.0 | 5 / 9 | |
| 1.1.4 | 3 / 7 | |
| 1.1.3 | 3 / 7 | |
| 1.1.2 | 3 / 7 | |
| 1.1.1 | 3 / 2 | |
| 1.1.0 | 3 / 2 | |
| 1.0.5 | 3 / 2 | |
| 1.0.2 | 3 / 2 | |
| 1.0.1 | 3 / 2 | |
| 1.0.0 | 3 / 2 |
v1.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.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.