wip: Cf worker experiment

[kumavis]

playing around with running on a Cloudflare Worker. got the kernel working but died by a thousand cuts fighting tooling.

also its pretty much all machine slop (gpt5 + claude-4.5-sonnet)

kernel-store/src/write-behind.ts might be useful, it does an in-memory store and then writes asyncly to a db

im sure im holding things wrong.

• project wide yarn build fails for some reason, including ts-link failing to rm dist dirs (??).
• vat build failing
  • ✘ [ERROR] error during vat operations: message: 'Cannot redefine property: name',

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​cloudflare/​workerd-windows-64@​1.20251001.0
	@​cloudflare/​workerd-linux-arm64@​1.20251001.0
	@​cloudflare/​workerd-darwin-arm64@​1.20251001.0
	@​cloudflare/​workerd-linux-64@​1.20251001.0
	@​cloudflare/​workerd-darwin-64@​1.20251001.0
	@​img/​sharp-darwin-arm64@​0.33.5
	@​img/​sharp-darwin-x64@​0.33.5
	@​img/​sharp-linux-arm64@​0.33.5
	@​img/​sharp-linux-arm@​0.33.5
	@​img/​sharp-linux-s390x@​0.33.5
	@​img/​sharp-linux-x64@​0.33.5
	@​img/​sharp-linuxmusl-arm64@​0.33.5
	@​img/​sharp-linuxmusl-x64@​0.33.5
	simple-swizzle@​0.2.4
	blake3-wasm@​2.1.5
	glob-to-regexp@​0.4.1
	@​cspotcode/​source-map-support@​0.8.1
	@​img/​sharp-libvips-darwin-arm64@​1.0.4
	@​img/​sharp-libvips-darwin-x64@​1.0.4
	@​img/​sharp-libvips-linux-arm64@​1.0.4
	@​img/​sharp-libvips-linux-arm@​1.0.5
	@​img/​sharp-libvips-linux-s390x@​1.0.4
	@​img/​sharp-libvips-linux-x64@​1.0.4
	@​img/​sharp-libvips-linuxmusl-arm64@​1.0.4
	@​img/​sharp-libvips-linuxmusl-x64@​1.0.4
	exit-hook@​2.2.1
	defu@​6.1.4
	kleur@​4.1.5
	error-stack-parser-es@​1.0.5
	@​speed-highlight/​core@​1.2.7
	@​cloudflare/​kv-asset-handler@​0.4.0
	stoppable@​1.1.0
	acorn-walk@​8.3.2
See 18 more rows in the dashboard

View full report

[socket-security]

Caution

MetaMask internal reviewing guidelines:

• Do not ignore-all
• Each alert has instructions on how to review if you don't know what it means. If lost, ask your Security Liaison or the supply-chain group
• Copy-paste ignore lines for specific packages or a group of one kind with a note on what research you did to deem it safe.
  @SocketSecurity ignore npm/PACKAGE@VERSION

Action	Severity	Alert  (click "▶" to expand/collapse)
Block		[email protected] has Network access. Module: globalThis["fetch"] Location: Package overview From: yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		[email protected] has Network access. Module: https Location: Package overview From: yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		[email protected] has Network access. Module: globalThis["fetch"] Location: Package overview From: yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is network access? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		[email protected] is a AI-detected potential code anomaly. Notes: The script is a standard post-install installer for native bindings: it downloads a prebuilt native binary and patches index.js to prefer the native implementation. I found no direct evidence of malicious intent in this file (no obfuscation, no data exfiltration, no eval). However, the behavior of downloading and executing a remote native binary and honoring an environment variable that can point to an arbitrary repository introduces a supply-chain risk. If an attacker can control the release artifacts, the BLAKE3_REPO_URL environment variable, or DNS/redirects for the download URL, they could cause arbitrary native code execution during install. Recommend verifying release integrity (checksums/signatures) and protecting environment variables in CI/deployment to reduce risk. Confidence: 1.00 Severity: 0.60 From: yarn.lock → npm/[email protected] ℹ Read more on: This package | This alert | What is an AI-detected potential code anomaly? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected]. Suggestion: An AI system found a low-risk anomaly in this package. It may still be fine to use, but you should check that it is safe before proceeding. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report