← Home

@ethereum-waffle/chai

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

ethworks

Keywords

ethereumsmart-contractssoliditytestingjavascripttypescriptlibrary

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): Added dep is `debug`, a trusted ubiquitous logging lib. ai
publish-pattern dormant-publish AI (publish-pattern): Routine monorepo release cadence, not account takeover indicator. ai
typosquat typosquat.levenshtein:chalk AI (typosquat): Established Ethereum testing library; name similarity to chalk is coincidental. ai
typosquat typosquat.levenshtein:hapi AI (typosquat): Established Ethereum testing library; name similarity to hapi is coincidental. ai

Versions (showing 11 of 11)

Version Deps Published
4.0.10 3 / 7
4.0.9 3 / 7
4.0.8 3 / 7
4.0.7 3 / 5
4.0.6 3 / 5
4.0.5 3 / 5
4.0.4 3 / 5
4.0.3 3 / 5
4.0.2 3 / 5
4.0.1 3 / 5
4.0.0 2 / 0

v4.0.9

1 finding
LOW No provenance attestation provenance

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

v4.0.8

1 finding
LOW No provenance attestation provenance

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

v4.0.7

1 finding
LOW No provenance attestation provenance

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

v4.0.6

1 finding
LOW No provenance attestation provenance

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

v4.0.5

1 finding
LOW No provenance attestation provenance

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

v4.0.4

1 finding
LOW No provenance attestation provenance

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

v4.0.3

1 finding
LOW No provenance attestation provenance

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

v4.0.2

1 finding
LOW No provenance attestation provenance

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

v4.0.1

1 finding
LOW No provenance attestation provenance

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

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