← Home

@exodus/solana-plugin

Solana plugin for Exodus SDK powered wallets.

85
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

joshuabot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Exodus org migrated to GitHub Actions CI publishing; stable pattern across their packages. ai
publish-pattern new-deps-added AI (publish-pattern): @exodus/basic-utils is a first-party Exodus package; addition is consistent with the package's ecosystem context. ai
maintainer-change maintainer-added AI (maintainer-change): Exodus org regularly rotates team members; changes are within the same organization. ai
maintainer-change maintainer-removed AI (maintainer-change): Removal of prior maintainers consistent with org team rotation, not a hostile takeover. ai
dependencies unvetted-dep:minimalistic-assert AI (dependencies): minimalistic-assert is a well-known, minimal utility with no malicious history; stable false positive for this package. ai
dependencies unvetted-dep:@exodus/i18n-dummy AI (dependencies): First-party Exodus stub/dummy i18n package; consistent with the org's publishing pattern. ai
provenance no-provenance AI (provenance): publishConfig explicitly sets provenance:false; stable policy for this publisher. ai

Versions (showing 85 of 85)

Version Deps Published
1.39.3 12 / 1
1.39.2 12 / 1
1.39.0 11 / 1
1.38.0 11 / 1
1.37.1 11 / 1
1.37.0 11 / 1
1.36.5 11 / 1
1.36.4 11 / 1
1.36.3 11 / 1
1.36.2 11 / 1
1.36.1 11 / 1
1.36.0 11 / 1
1.35.0 11 / 1
1.33.0 11 / 1
1.32.4 11 / 1
1.32.3 11 / 1
1.32.2 11 / 1
1.32.1 11 / 1
1.32.0 11 / 1
1.31.0 11 / 1
1.30.5 11 / 1
1.30.4 11 / 1
1.30.2 11 / 1
1.30.1 11 / 1
1.30.0 11 / 1
1.29.3 11 / 1
1.29.2 11 / 1
1.29.1 11 / 1
1.29.0 11 / 1
1.28.2 11 / 1
1.28.1 11 / 1
1.28.0 11 / 1
1.27.0 11 / 1
1.26.0 11 / 1
1.25.0 11 / 1
1.24.6 11 / 1
1.24.5 11 / 1
1.24.4 11 / 1
1.24.2 11 / 1
1.24.1 11 / 1
1.23.2 8 / 1
1.23.1 8 / 1
1.23.0 8 / 1
1.22.0 8 / 1
1.21.1 8 / 1
1.21.0 8 / 1
1.20.1 8 / 1
1.20.0 8 / 1
1.19.0 8 / 1
1.18.3 8 / 1
1.18.2 8 / 1
1.18.1 8 / 1
1.18.0 8 / 1
1.17.1 8 / 1
1.17.0 8 / 1
1.16.7 8 / 1
1.16.6 8 / 1
1.16.5 8 / 1
1.16.4 8 / 1
1.16.3 8 / 1
1.16.2 8 / 1
1.16.1 8 / 1
1.16.0 8 / 1
1.15.2 8 / 1
1.15.1 8 / 1
1.15.0 8 / 1
1.14.3 8 / 1
1.14.2 8 / 1
1.14.1 8 / 1
1.14.0 8 / 1
1.13.0 8 / 1
1.12.5 8 / 1
1.12.4 8 / 1
1.12.3 8 / 1
1.12.2 8 / 1
1.12.1 8 / 1
1.12.0 8 / 1
1.11.0 8 / 1
1.10.1 8 / 1
1.10.0 8 / 1
1.9.2 8 / 1
1.9.1 8 / 1
1.9.0 8 / 1
1.8.1 7 / 1
1.8.0 7 / 1

v1.20.1

1 finding
INFO No provenance attestation provenance

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

v1.20.0

1 finding
INFO No provenance attestation provenance

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

v1.19.0

1 finding
INFO No provenance attestation provenance

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

v1.18.3

1 finding
INFO No provenance attestation provenance

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

v1.18.2

1 finding
INFO No provenance attestation provenance

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

v1.18.1

1 finding
INFO No provenance attestation provenance

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

v1.18.0

1 finding
INFO No provenance attestation provenance

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

v1.17.1

1 finding
INFO No provenance attestation provenance

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

v1.17.0

1 finding
INFO No provenance attestation provenance

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

v1.16.7

1 finding
INFO No provenance attestation provenance

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

v1.16.6

1 finding
INFO No provenance attestation provenance

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

v1.16.5

1 finding
INFO No provenance attestation provenance

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

v1.16.4

1 finding
INFO No provenance attestation provenance

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

v1.16.3

1 finding
INFO No provenance attestation provenance

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

v1.16.2

1 finding
INFO No provenance attestation provenance

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

v1.16.1

1 finding
INFO No provenance attestation provenance

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

v1.16.0

1 finding
INFO No provenance attestation provenance

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

v1.15.2

1 finding
INFO No provenance attestation provenance

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

v1.15.1

1 finding
INFO No provenance attestation provenance

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

v1.15.0

1 finding
INFO No provenance attestation provenance

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

v1.14.3

1 finding
INFO No provenance attestation provenance

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

v1.14.2

1 finding
INFO No provenance attestation provenance

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

v1.14.1

1 finding
INFO No provenance attestation provenance

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

v1.14.0

1 finding
INFO No provenance attestation provenance

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

v1.13.0

1 finding
INFO No provenance attestation provenance

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

v1.12.5

1 finding
INFO No provenance attestation provenance

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

v1.12.4

1 finding
INFO No provenance attestation provenance

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

v1.12.3

1 finding
INFO No provenance attestation provenance

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

v1.12.2

1 finding
INFO No provenance attestation provenance

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

v1.12.1

1 finding
INFO No provenance attestation provenance

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

v1.12.0

1 finding
INFO No provenance attestation provenance

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

v1.11.0

1 finding
INFO No provenance attestation provenance

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

v1.10.1

1 finding
INFO No provenance attestation provenance

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

v1.10.0

1 finding
INFO No provenance attestation provenance

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

v1.9.2

1 finding
INFO No provenance attestation provenance

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

v1.9.1

1 finding
INFO No provenance attestation provenance

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

v1.9.0

1 finding
INFO No provenance attestation provenance

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

v1.8.1

1 finding
INFO No provenance attestation provenance

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

v1.8.0

1 finding
INFO No provenance attestation provenance

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