← Home

@cloudflare/worker-bundler

npm Repository Homepage

Build and bundle Workers at runtime for Cloudflare Worker Loader binding

5
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

rexscariadcruz_cfjculveysejokercf-radarcf-ci-writesegments-writethibmeuxortivecf-ci2lvalentaworengathird774jasnellterinjokescelsojsteinbergergregbrimbleasapzacyg4brymwrangler-publishercf-media-managerdash_service_accountlerwincfcf-npm-publishsimonabadoiucms1919mgirouard-cfmusa-cfvaishakpdineshichernetsky-cfjseba_cfgabivlj-cfganders-cloudflarensharma-cfmikenomitchtlefebvre_cfnafeezcfeduardo-vargasthreepointonextuc

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/typescript.js AI (source-diff): Bundled TypeScript compiler shipped as minified dist artifact; expected for a worker bundler package. ai
provenance publisher-changed AI (provenance): Transition to GitHub Actions CI publisher with SLSA provenance; legitimate Cloudflare org CI/CD migration. ai
maintainer-change maintainer-added AI (maintainer-change): cf-npm-publish is Cloudflare's CI publish account; consistent with org-level automation. ai
npm-metadata suspicious-initial-version AI (npm-metadata): 0.0.0 is a Cloudflare monorepo placeholder pattern; publisher is a trusted long-standing contributor. ai
bogus-package bogus-package AI (bogus-package): Stub/namespace-reservation package in @cloudflare scope from trusted publisher; structural signals are expected. ai

Versions (showing 5 of 5)

Version Deps Published
0.1.3 8 / 1
0.1.2 8 / 1
0.1.1 8 / 1
0.1.0 8 / 1
0.0.0 0 / 0

v0.1.3

1 finding
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.1.2

3 findings
HIGH Publisher changed: threepointone → GitHub Actions (on 2026-04-18) provenance

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

HIGH New obfuscated file: dist/typescript.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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

3 findings
HIGH Publisher changed: threepointone → GitHub Actions (on 2026-04-13) provenance

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

HIGH New obfuscated file: dist/typescript.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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

3 findings
HIGH Publisher changed: threepointone → GitHub Actions (on 2026-04-11) provenance

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

HIGH New obfuscated file: dist/typescript.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

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