← Home

@solana-developers/helpers

npm Repository Homepage
12
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

solana-devsnickfrosty

Keywords

solanablockchainsecret keyprivate keykeypairdevnet SOLfaucet

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
semgrep semgrep:shady-links-raw-ip AI (semgrep): Localhost test-validator URL in test file, not real exfil target. ai
maintainer-change maintainer-removed AI (maintainer-change): Org package with trusted long-standing publisher; not a takeover pattern. ai
publish-pattern dormant-publish AI (publish-pattern): Normal release cadence for a stable helper library, not suspicious. ai
publish-pattern new-deps-added AI (publish-pattern): @coral-xyz/anchor is a well-known Solana ecosystem package. ai
phantom-deps phantom-dep:dotenv AI (phantom-deps): dotenv used via config/env loading, not a real risk. ai

Versions (showing 12 of 12)

Version Deps Published
2.8.1 7 / 6
2.8.0 7 / 6
2.7.0 6 / 6
2.6.0 6 / 5
2.5.6 5 / 5
2.5.5 5 / 5
2.5.4 5 / 6
2.5.3 5 / 6
2.5.2 5 / 6
2.5.1 5 / 6
2.5.0 5 / 6
2.4.0 4 / 6

v2.8.0

1 finding
LOW No provenance attestation provenance

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

v2.7.0

1 finding
LOW No provenance attestation provenance

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

v2.6.0

1 finding
LOW No provenance attestation provenance

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

v2.5.6

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mikemaccana → nickfrosty (on 2024-09-27, known maintainer) provenance

This version was published by a different npm account (nickfrosty) than the most recent previously approved version (mikemaccana) on 2024-09-27, but nickfrosty is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v2.5.5

1 finding
LOW No provenance attestation provenance

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

v2.5.4

1 finding
LOW No provenance attestation provenance

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

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

v2.5.2

2 findings
HIGH shady-links-raw-ip: src/index.test.ts:39 semgrep

HTTP request to raw IP address — legitimate packages use domain names 37 | const exec = promisify(execNoPromises); 38 | > 39 | const LOCALHOST = "http://127.0.0.1:8899"; 40 | const MEMO_PROGRAM_ID = new PublicKey( 41 | "MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr",

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

2 findings
HIGH shady-links-raw-ip: src/index.test.ts:39 semgrep

HTTP request to raw IP address — legitimate packages use domain names 37 | const exec = promisify(execNoPromises); 38 | > 39 | const LOCALHOST = "http://127.0.0.1:8899"; 40 | const MEMO_PROGRAM_ID = new PublicKey( 41 | "MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr",

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

2 findings
HIGH shady-links-raw-ip: src/index.test.ts:39 semgrep

HTTP request to raw IP address — legitimate packages use domain names 37 | const exec = promisify(execNoPromises); 38 | > 39 | const LOCALHOST = "http://127.0.0.1:8899"; 40 | const MEMO_PROGRAM_ID = new PublicKey( 41 | "MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr",

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

2 findings
HIGH shady-links-raw-ip: src/index.test.ts:36 semgrep

HTTP request to raw IP address — legitimate packages use domain names 34 | const exec = promisify(execNoPromises); 35 | > 36 | const LOCALHOST = "http://127.0.0.1:8899"; 37 | const MEMO_PROGRAM_ID = new PublicKey( 38 | "MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr",

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.