← Home

@reservoir0x/relay-solana-wallet-adapter

6
Versions
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

jadendurnfordted-palmeripelegilingzizsepicoptrwttspedromcunha-unevengeorgeroman

Keywords

solanareservoirrelay-solana-wallet-adapterreservoir-solana-wallet-adapterrelayprotocolsdk-adapter

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:hex-decode AI (semgrep): Hex decoding is standard Solana instruction data handling; not obfuscation or malicious payload. ai
phantom-deps phantom-dep:axios AI (phantom-deps): Declared dependency used via config/indirect import; stable false positive for this package. ai
phantom-deps phantom-dep:@types/node AI (phantom-deps): Type-only package loaded by convention; not directly imported in source. ai

Versions (showing 6 of 6)

Version Deps Published
2.0.5 2 / 1
2.0.4 2 / 1
2.0.3 2 / 1
2.0.2 2 / 1
2.0.1 2 / 1
2.0.0 2 / 1

v2.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.1

1 finding
LOW No provenance attestation provenance

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
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.