← Home

@exodus/basemainnet-plugin

npm Repository Homepage

Base Mainnet plugin for Exodus SDK powered wallets

22
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 Movement migrated publishing to GitHub Actions CI; consistent across their package ecosystem. ai
bogus-package bogus-package AI (bogus-package): Internal SDK plugin from Exodus Movement; sparse README/keywords are expected for org-internal packages. ai
provenance no-provenance AI (provenance): publishConfig explicitly sets provenance:false; intentional org policy, not an oversight. ai

Versions (showing 22 of 22)

Version Deps Published
2.10.3 2 / 4
2.10.2 2 / 3
2.10.1 2 / 3
2.10.0 2 / 3
2.9.0 2 / 2
2.8.0 2 / 2
2.7.3 2 / 2
2.7.2 2 / 2
2.7.1 2 / 2
2.7.0 2 / 2
2.6.0 2 / 2
2.5.0 2 / 1
2.4.2 2 / 1
2.4.1 2 / 1
2.4.0 2 / 1
2.3.3 2 / 1
2.3.2 2 / 1
2.3.1 2 / 1
2.3.0 2 / 1
2.2.0 3 / 1
2.1.0 4 / 1
2.0.0 4 / 1

v2.3.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.

v2.3.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.

v2.3.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.

v2.3.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.

v2.2.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.

v2.1.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.

v2.0.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.