← Home

@aztec/entrypoints

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

Maintainers

zac-williamsonleilawangcharlielyejaosefjoss-aztecprotocolludamad

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
dependencies unvetted-dep:@aztec/standard-contracts AI (dependencies): Same-org sibling package pinned to identical version, standard monorepo pattern. ai
phantom-deps phantom-dep:@aztec/protocol-contracts AI (phantom-deps): Same-org sibling, likely re-exported/used indirectly. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is explicitly declared in package.json dependencies; it is used implicitly by TypeScript-compiled ESM output. This is a stable false positive for all @aztec/* packages. ai
bogus-package bogus-package AI (bogus-package): Monorepo sub-package; short README and missing keywords are expected for internal packages not intended for standalone npm discovery. Not a spam/low-value signal for this ecosystem. ai

Versions (showing 27 of 27)

Version Deps Published
5.0.0 7 / 6
4.4.0 6 / 6
4.3.1 6 / 6
4.3.0 6 / 6
4.2.1 6 / 6
4.2.0 6 / 6
4.1.3 6 / 6
4.1.2 6 / 6
4.1.1 6 / 6
4.1.0 6 / 6
4.0.4 6 / 6
4.0.3 6 / 6
4.0.2 6 / 6
4.0.1 6 / 6
3.0.3 6 / 6
3.0.2 6 / 6
3.0.1 6 / 6
2.1.11 5 / 5
2.1.9 5 / 5
2.1.8 5 / 5
2.1.7 5 / 5
2.1.6 5 / 5
2.1.5 5 / 5
2.1.4 5 / 5
2.1.3 5 / 5
2.1.2 5 / 5
2.0.4 5 / 5

v5.0.0

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: charlielye.

LOW No provenance attestation provenance

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

v4.4.0

1 finding
LOW No provenance attestation provenance

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