← Home

@huggingface/xetchunk-wasm

npm Repository Homepage
5
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

julien-cpierriccoyotte508xenovagary149

Keywords

xetchunkchunking

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance no-provenance AI (provenance): HuggingFace org package; lack of provenance is common and not a risk signal here. ai
provenance publisher-changed AI (provenance): Hugging Face org migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern going forward. ai
provenance missing-githead AI (provenance): SLSA provenance attestation supersedes gitHead as supply chain integrity signal for this package. ai
dependencies unvetted-dep:gearhash-jit AI (dependencies): workspace:* monorepo sibling; not an external npm dependency. ai
dependencies unvetted-dep:@huggingface/blake3-jit AI (dependencies): workspace:* monorepo sibling; not an external npm dependency. ai

Versions (showing 5 of 5)

Version Deps Published
0.1.0 2 / 1
0.0.6 2 / 1
0.0.4 2 / 1
0.0.3 2 / 1
0.0.1 2 / 2

v0.1.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

v0.0.6

3 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

HIGH Publisher changed: coyotte508 → GitHub Actions (on 2026-05-08) provenance

This version was published by a different npm account than previous versions on 2026-05-08. This could indicate a legitimate maintainer transition or an account compromise.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v0.0.4

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

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.