← Home

@lit-protocol/uint8arrays

npm Repository Homepage
20
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

glitch003adarsh-kumar28websaamhwrdtmfamuramaximushaximusspacesailorawisniew

Keywords

library

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern dormant-publish AI (publish-pattern): Known maintainer publishing on established monorepo; no malicious behavior evidenced. ai
maintainer-change maintainer-removed AI (maintainer-change): famura is a known prior maintainer per provenance INFO, not a takeover. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): Known implicit runtime dependency; stable pattern. ai
phantom-deps phantom-dep:ethers AI (phantom-deps): Config-referenced dependency in monorepo build; stable pattern. ai
phantom-deps phantom-dep:@openagenda/verror AI (phantom-deps): Config-referenced dependency in monorepo build; stable pattern. ai
phantom-deps phantom-dep:depd AI (phantom-deps): Config-referenced dependency in monorepo build; stable pattern. ai
phantom-deps phantom-dep:@lit-protocol/contracts AI (phantom-deps): Same-org monorepo dependency; stable pattern. ai
phantom-deps phantom-dep:@lit-protocol/accs-schemas AI (phantom-deps): Same-org monorepo dependency; stable pattern. ai
phantom-deps phantom-dep:@ethersproject/abstract-provider AI (phantom-deps): Config-referenced dependency in monorepo build; stable pattern. ai
phantom-deps phantom-dep:@lit-protocol/types AI (phantom-deps): Same-org monorepo dependency; stable pattern. ai
phantom-deps phantom-dep:siwe AI (phantom-deps): Config-referenced dependency in monorepo build; stable pattern. ai

Versions (showing 20 of 20)

Version Deps Published
7.4.0 10 / 0
7.3.1 10 / 0
7.3.0 10 / 0
7.2.3 7 / 0
7.2.1 10 / 0
7.2.0 10 / 0
7.1.3 10 / 0
7.1.2 10 / 0
7.1.1 10 / 0
7.1.0 10 / 0
7.0.9 10 / 0
7.0.8 10 / 0
7.0.7 10 / 0
7.0.6 10 / 0
7.0.5 10 / 0
7.0.4 10 / 0
7.0.3 10 / 0
7.0.2 10 / 0
7.0.1 10 / 0
7.0.0 9 / 0

v7.2.3

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: websaam → glitch003 (on 2025-08-05, known maintainer) provenance

This version was published by a different npm account (glitch003) than the most recent previously approved version (websaam) on 2025-08-05, but glitch003 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.

v7.1.1

1 finding
LOW No provenance attestation provenance

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

v7.1.0

1 finding
LOW No provenance attestation provenance

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

v7.0.9

1 finding
LOW No provenance attestation provenance

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

v7.0.8

1 finding
LOW No provenance attestation provenance

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

v7.0.7

1 finding
LOW No provenance attestation provenance

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

v7.0.6

1 finding
LOW No provenance attestation provenance

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

v7.0.5

1 finding
LOW No provenance attestation provenance

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

v7.0.4

1 finding
LOW No provenance attestation provenance

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

v7.0.3

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: websaam → famura (on 2024-12-23, known maintainer) provenance

This version was published by a different npm account (famura) than the most recent previously approved version (websaam) on 2024-12-23, but famura 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.

v7.0.2

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: websaam → famura (on 2024-12-09, known maintainer) provenance

This version was published by a different npm account (famura) than the most recent previously approved version (websaam) on 2024-12-09, but famura 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.

v7.0.1

1 finding
LOW No provenance attestation provenance

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

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