← Home

@chenglou/pretext

npm Repository Homepage
4
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

chenglou

Keywords

text-layouttext-measurementline-breakingtypographycanvassvgunicode

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
npm-metadata suspicious-initial-version AI (npm-metadata): Publisher chenglou has 4058-day history; 0.0.0 is a legitimate semver choice for early development. Not suspicious in context. ai
provenance no-provenance AI (provenance): No provenance is common (~88% of npm packages); not a meaningful risk signal for this established publisher. ai

Versions (showing 4 of 4)

Version Deps Published
0.0.8 0 / 7
0.0.7 0 / 6
0.0.6 0 / 6
0.0.5 0 / 6

v0.0.8

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

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

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

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.