← Home

@ewizardjs/builder-utils

npm Repository
17
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

serhii_butvasylshylovewizardjs-teamb.hryhorievm.polevchukv.kobyletskiyalexbelov

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): lodash.merge is a well-established utility; no malicious indicators in this addition. ai
semgrep semgrep:dynamic-require AI (semgrep): Fires on env-var-driven manifest require in a build tool entry; stable pattern across versions. ai
phantom-deps phantom-dep:sass AI (phantom-deps): Referenced in config files only; stable false positive for this build-utils package. ai
phantom-deps phantom-dep:js-beautify AI (phantom-deps): Referenced in config files only; stable false positive for this build-utils package. ai

Versions (showing 17 of 17)

Version Deps Published
6.8.1 77 / 49
6.7.1 76 / 48
6.7.0 76 / 48
6.6.2 75 / 47
6.6.1 75 / 47
6.6.0 75 / 47
6.5.3 75 / 47
6.5.0 75 / 47
6.4.3 75 / 47
6.4.2 75 / 47
6.3.2 75 / 47
6.3.0 75 / 47
6.2.0 74 / 46
6.1.1 74 / 43
6.1.0 73 / 43
6.0.1 73 / 43
6.0.0 71 / 44

v6.2.0

1 finding
LOW No provenance attestation provenance

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

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

v6.1.0

1 finding
LOW No provenance attestation provenance

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

v6.0.1

1 finding
LOW No provenance attestation provenance

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

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