Breaking: Java4Shell (CVE-2026-114938) - Less Than 0.12% of JVMs Estimated at Risk of RCE
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

streamfold

Latest version: v0.1.20

Overview

Last scanned
18 Nov 2026
Published
18 Nov 2026
npm package Publisher: agentbase-bot, kinfish, okisdev, yonom
3 Stars
0 Forks
15 Versions
2.4K Downloads
Rust Repo language

Scan summary

streamfold was last scanned on 18 Nov 2026 at version 0.1.20. Risk score 5 of 100 (low). No malicious behavior was detected.

  • Releases: 15 versions; the latest 2 were published on 18 Nov 2026.
  • Findings: 1 rule fired in version 0.1.20 (1 low). The score describes this version only.
  • Downloads: 2,391 downloads.

Versions

15 versions published
Versions and the rules that fired in each
VersionPublishedStatus
0.1.20 LATEST 18 Nov 2026 1 rule fired
0.1.19 18 Nov 2026 No rules fired
0.1.18 4 Nov 2026 No rules fired
0.1.17 4 Nov 2026 Not shown
0.1.16 2 Nov 2026 Not shown

Rules fired in 0.1.20: 1

Findings

1 Low

Findings for v0.1.20. The score is a capped sum of the weights of the rules that fired — not CVSS, not exploitability, and not a probability. It is not comparable across packages with different scan coverage.

Maintainer or owner changed

The package's maintainer or owner differs from the previous version. This is usually benign, such as a transfer or reorganization, but account takeovers look the same at first. Shown for awareness.

LOW
Checking access…

🔒 Create a free account to see all 1 finding with descriptions and instance counts

The score describes 0.1.20; other versions have their own rules, not their own score.

README

The publisher’s own README, as collected from the registry.

streamfold

Incremental structured state for streamed AI tool calls.

Streamfold retains JSON parser and value state across deltas. Its embedded Rust/WebAssembly engine emits compact patches and works in Node.js 20+ and modern browsers without native build tools or provider SDK dependencies.

Install

npm install streamfold

Quick start

import { createStructuredStream } from "streamfold";

const stream = createStructuredStream();
const update = stream.push('{"city":"San');

console.log(update.partialValue); // { city: "San" }

stream.push(' Francisco"}');
console.log(stream.getFieldState(["city"])); // "complete"

stream.finish();
stream.dispose();

Values are live by default. Use createStructuredStream({ snapshots: "immutable" }) for frozen snapshots that preserve earlier values and share unchanged branches. Pools and custom adapter factories accept the same option; managed readers forward it through limits.

Chunks must contain well-formed Unicode. Valid surrogate pairs may span chunks; raw unpaired UTF-16 code units fail with INVALID_CHUNK instead of being silently replaced during UTF-8 encoding. Use JSON Unicode escapes for unpaired code units (as produced by JSON.stringify).

Use streamfold/assistant-ui, streamfold/vercel-ai, streamfold/openai, streamfold/anthropic, streamfold/gemini, streamfold/langchain, or streamfold/ag-ui for decoded SDK events. Integrations use structural event types and do not load provider SDKs.

For custom protocols, import defineAdapter from streamfold. Translate each event into an array of start, delta, end, or abort operations. The returned factory creates an independent session with pushAll(event), finish(), and dispose(). See the API reference for a complete switch-based example.

For automatic lifecycle management, use readStructured(events, { adapter, limits }) in a for await loop. It wraps the same batch adapter, finalizes remaining calls at the end of the source, and disposes on completion, failure, or early exit. limits is optional. For a built-in SDK factory, use { integration: assistantUI, limits } instead. Both paths yield the same lifecycle updates without replaying completions. Readable streams are consumed through getReader() even without an abort signal or native async-iterator support. Upstream failures close the iterator or reader while preserving the original error, even when no abort signal is supplied.

Every built-in adapter supports pushAll(event), returning all ordered start, update, and complete updates, including multiple calls in one event. Existing push(event) remains available. Call finish() at the stream boundary.

Pass onDiagnostic in a custom factory's options, as an SDK factory's second argument, or beside the factory in readStructured. Errors preserve their native categories and include structured codes and call context where known.

See the repository for the API reference, integration guide, and benchmarks.

MIT © Streamfold contributors

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.

Where it’s listed

The probe returned only these fields for this server — auth requirement, protocol and tool list weren’t observed, so they’re not shown (never guessed).

  • npm streamfold

References

The publisher’s own links, as the registry reports them. These are not sources for the assessment on this page.

Scan your whole stack

Group 1261154050 1
Group 1261154050
 

From OX Research Newsroom

Nodejs Brotli Flaw
CVE

Node.js Brotli Decoder Out-of-Bounds Write (RCE) – CVE-2026-111497

Critical Apache HTTP Server Flaw Exposes Web Servers to RCE (1)
CVE

CVE-2026-119618: Critical Apache HTTP Server Flaw Exposes Web Servers to Remote Code Execution

CVE

Java4Shell (CVE-2026-114938): Easy to Crash, Hard to Exploit — Less Than 0.12% of JVMs Estimated at Risk of RCE

Frame 2085668439 (1)
Group 1261154229