← Home

pagefind

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

bglw

Keywords

jamstackstaticsearchpagefindpagefind

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): gitHead dropped because publish moved to SLSA-attested CI/CD; benign env change. ai
phantom-deps phantom-dep:@pagefind/darwin-arm64 AI (phantom-deps): Platform-specific optional binary, expected not to be imported. ai
phantom-deps phantom-dep:@pagefind/linux-arm64 AI (phantom-deps): Platform-specific optional binary, expected not to be imported. ai
phantom-deps phantom-dep:@pagefind/windows-x64 AI (phantom-deps): Platform-specific optional binary, expected not to be imported. ai
phantom-deps phantom-dep:@pagefind/linux-x64 AI (phantom-deps): Platform-specific optional binary, expected not to be imported. ai
phantom-deps phantom-dep:@pagefind/darwin-x64 AI (phantom-deps): Platform-specific optional binary, expected not to be imported. ai
semgrep semgrep:child-process-import AI (semgrep): CLI binary entry point uses spawnSync to launch platform-native pagefind binary distributed via optional deps; this is the documented and expected architecture for this tool. ai
semgrep semgrep:base64-decode AI (semgrep): Standard cross-environment base64 decode utility in lib/encoding.js; no obfuscation or malicious payload — expected for a library handling binary search index data. ai

Versions (showing 6 of 6)

Version Deps Published
1.5.2 0 / 1
1.5.0 0 / 1
1.4.0 0 / 1
1.3.0 0 / 1
1.2.0 0 / 1
1.1.1 0 / 1

v1.5.2

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

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.

v1.5.0

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.

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 Publisher changed: bglw → GitHub Actions (on 2026-04-06, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (bglw) on 2026-04-06, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v1.3.0

1 finding
LOW No provenance attestation provenance

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

v1.2.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.

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