← Home

@bananapus/core-v6

npm Repository Homepage
28
Versions
—
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

simplemachineme.jangofilipviz

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@bananapus/address-registry-v6 AI (phantom-deps): Same-org Solidity dependency used as a Foundry remapping/config reference, not a JS import. Expected pattern for this package type. ai
dependencies unvetted-dep:@uniswap/permit2 AI (dependencies): Uniswap/permit2 is the canonical Uniswap repo; GitHub-pinned deps are standard in Foundry/Solidity projects where npm registry versions don't exist. Stable pattern for this package. ai
npm-metadata url-dep:@uniswap/permit2 AI (npm-metadata): GitHub URL dep on Uniswap/permit2 is a well-known Foundry ecosystem pattern; the dep is a phantom (used only in config/remappings, not JS runtime). Stable for this package. ai
bogus-package bogus-package AI (bogus-package): README link density reflects multi-chain contract deployment addresses and audit links, not a phishing link farm. Consistent with Bananapus smart contract package style. ai
phantom-deps phantom-dep:@prb/math AI (phantom-deps): Foundry/Solidity package; deps are referenced in remappings/config files, not JS imports. This is the expected pattern for this package type. ai
phantom-deps phantom-dep:@bananapus/permission-ids-v6 AI (phantom-deps): Foundry/Solidity package; same-org dep referenced in config files, not JS imports. Expected pattern. ai
phantom-deps phantom-dep:@uniswap/permit2 AI (phantom-deps): Foundry/Solidity package; deps are referenced in remappings/config files, not JS imports. This is the expected pattern for this package type. ai
phantom-deps phantom-dep:@chainlink/contracts AI (phantom-deps): Foundry/Solidity package; deps are referenced in remappings/config files, not JS imports. This is the expected pattern for this package type. ai
phantom-deps phantom-dep:@openzeppelin/contracts AI (phantom-deps): Foundry/Solidity package; deps are referenced in remappings/config files, not JS imports. This is the expected pattern for this package type. ai

Versions (showing 28 of 28)

Version Deps Published
0.0.55 5 / 1
0.0.47 5 / 1
0.0.37 5 / 1
0.0.36 5 / 1
0.0.35 5 / 1
0.0.34 5 / 1
0.0.33 5 / 1
0.0.32 5 / 1
0.0.31 5 / 1
0.0.30 6 / 1
0.0.28 6 / 1
0.0.27 6 / 1
0.0.26 6 / 1
0.0.25 5 / 1
0.0.23 5 / 1
0.0.22 5 / 1
0.0.20 5 / 1
0.0.19 5 / 1
0.0.18 5 / 1
0.0.15 5 / 1
0.0.11 5 / 1
0.0.9 5 / 1
0.0.7 5 / 1
0.0.6 5 / 1
0.0.4 5 / 1
0.0.3 5 / 1
0.0.2 5 / 1
0.0.1 5 / 1

v0.0.55

1 finding
LOW No provenance attestation provenance

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

v0.0.47

1 finding
LOW No provenance attestation provenance

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

v0.0.37

1 finding
LOW No provenance attestation provenance

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

v0.0.36

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.

v0.0.35

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.

v0.0.34

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.

v0.0.33

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.

v0.0.32

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.

v0.0.31

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.

v0.0.30

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.

v0.0.28

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.

v0.0.27

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.

v0.0.26

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.

v0.0.25

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.

v0.0.23

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.

v0.0.22

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.

v0.0.20

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.

v0.0.19

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.

v0.0.18

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.

v0.0.15

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.

v0.0.11

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.

v0.0.9

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.

v0.0.7

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.

v0.0.6

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.

v0.0.4

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.

v0.0.3

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.

v0.0.2

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.

v0.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.