← Home

@metaplex-foundation/beet-solana

npm Repository Homepage

Solana specific extension for beet, the borsh compatible de/serializer

14
Versions
Apache-2.0
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

danenbmnhanphanblockiosaurus0x_febosvc01-metaplexbrandontulsi

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
maintainer-change maintainer-added AI (maintainer-change): Added maintainers are known Metaplex org members, consistent with team growth. ai
publish-pattern new-deps-added AI (publish-pattern): bs58/debug are common, well-vetted utility libs matching feature scope. ai
source-diff source-size-tripled AI (source-diff): Small absolute size increase (7KB->24KB) consistent with added deps/features. ai
npm-metadata suspicious-initial-version AI (npm-metadata): Legit first release of established Metaplex package, not a throwaway. ai

Versions (showing 14 of 14)

Version Deps Published
0.4.1 4 / 10
0.4.0 4 / 10
0.3.1 4 / 10
0.3.0 4 / 10
0.2.0 2 / 8
0.1.1 2 / 7
0.1.0 2 / 7
0.0.6 2 / 7
0.0.5 2 / 7
0.0.4 2 / 7
0.0.3 2 / 7
0.0.2 2 / 7
0.0.1 2 / 7
0.0.0 2 / 7

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.1

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

v0.1.0

1 finding
LOW No provenance attestation provenance

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

v0.0.6

1 finding
LOW No provenance attestation provenance

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

v0.0.5

1 finding
LOW No provenance attestation provenance

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

v0.0.4

1 finding
LOW No provenance attestation provenance

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

v0.0.3

1 finding
LOW No provenance attestation provenance

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

v0.0.2

1 finding
LOW No provenance attestation provenance

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

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.

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