← Home

@umbra-privacy/umbra-codama

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

Maintainers

dev-umbra

Keywords

umbrasolanacodamaprivacyanchor

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@solana/kit AI (phantom-deps): Config-referenced Solana dependency in generated Codama client; stable pattern. ai
phantom-deps phantom-dep:@solana/sysvars AI (phantom-deps): Config-referenced Solana dependency in generated Codama client; stable pattern. ai
phantom-deps phantom-dep:@solana-program/system AI (phantom-deps): Config-referenced Solana dependency in generated Codama client; stable pattern. ai
phantom-deps phantom-dep:@solana-program/token-2022 AI (phantom-deps): Config-referenced Solana dependency in generated Codama client; stable pattern. ai

Versions (showing 3 of 3)

Version Deps Published
2.0.2 4 / 6
2.0.1 4 / 6
2.0.0 4 / 6

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

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.