← Home

@enhavo/translation

20
Versions
MIT
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

gseidel

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): No provenance across all versions of this package; not a risk indicator here. ai
bogus-package bogus-package AI (bogus-package): Scoped monorepo sub-package; sparse metadata is expected, not a spam/malware indicator. ai
npm-metadata no-description AI (npm-metadata): Monorepo sub-package pattern; missing description is cosmetic, not a risk signal here. ai

Versions (showing 20 of 20)

Version Deps Published
0.15.13 2 / 0
0.15.12 2 / 0
0.15.11 2 / 0
0.15.10 3 / 0
0.15.9 3 / 0
0.15.8 3 / 0
0.15.7 3 / 0
0.15.6 3 / 0
0.15.5 3 / 0
0.15.4 3 / 0
0.15.3 3 / 0
0.15.2 3 / 0
0.15.1 3 / 0
0.14.7 3 / 0
0.14.6 3 / 0
0.14.5 3 / 0
0.14.3 3 / 0
0.14.2 3 / 0
0.13.6 3 / 0
0.12.6 3 / 0

v0.14.3

1 finding
INFO No provenance attestation provenance

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

v0.14.2

1 finding
INFO No provenance attestation provenance

[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.13.6

1 finding
INFO No provenance attestation provenance

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

v0.12.6

1 finding
INFO No provenance attestation provenance

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