← Home

@daocloud-proto/zestu

npm
30
Versions
ISC
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

wilsonwulsq645599166daocloud-proto-robot

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:jest AI (typosquat): Scoped DaoCloud proto package; 'zestu' is unrelated to jest — stable false positive across all versions. ai
bogus-package bogus-package AI (bogus-package): Auto-generated proto stub packages routinely lack descriptions, repos, and deps; pattern is stable for this org. ai

Versions (showing 30 of 30)

Version Deps Published
0.16.0 0 / 0
0.15.0 0 / 0
0.14.0 0 / 0
0.13.1 0 / 0
0.13.0 0 / 0
0.12.0 0 / 0
0.11.0 0 / 0
0.10.3 0 / 0
0.10.2 0 / 0
0.10.1 0 / 0
0.10.0 0 / 0
0.9.0 0 / 0
0.8.0 0 / 0
0.7.0 0 / 0
0.6.1 0 / 0
0.6.0 0 / 0
0.5.5 0 / 0
0.5.4 0 / 0
0.5.3 0 / 0
0.5.2 0 / 0
0.5.1 0 / 0
0.5.0 0 / 0
0.4.1 0 / 0
0.4.0 0 / 0
0.3.2 0 / 0
0.3.1 0 / 0
0.3.0 0 / 0
0.2.1 0 / 0
0.2.0 0 / 0
0.1.0 0 / 0

v0.4.1

1 finding
LOW No provenance attestation provenance

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

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

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

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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