This release includes 3 security fixes for security teams reviewing exposed deployments.
Topics
+11 more
Affected surfaces
ReleasePort's take
Moderate signalThe release tightens npm packaging security by switching to an explicit runtime‑file allowlist and adding tracked‑file checks across CI pipelines, build steps, and diagnostic outputs.
Why it matters: Security severity scores exceed 70; mitigates risk of inadvertent inclusion of sensitive files (config, logs, sessions, databases, keys) in published packages. Immediate attention recommended for CI/CD maintainers.
Summary
AI summaryReplaced permissive npm packaging with an explicit runtime-file allowlist and added tracked‑file checks to secure environment data.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Security | Critical |
Replaced permissive npm packaging with an explicit runtime-file allowlist. Replaced permissive npm packaging with an explicit runtime-file allowlist. Source: llm_adapter@2026-07-17 Confidence: high |
— |
| Security | High |
Added tracked-file and final-tarball checks for sensitive files in CI, prepublishOnly, environment config, logs, sessions, databases, key material, and development worktrees. Added tracked-file and final-tarball checks for sensitive files in CI, prepublishOnly, environment config, logs, sessions, databases, key material, and development worktrees. Source: llm_adapter@2026-07-17 Confidence: high |
— |
| Security | High |
Removed provider‑shaped tokens from tracked visualization assets. Removed provider‑shaped tokens from tracked visualization assets. Source: llm_adapter@2026-07-17 Confidence: high |
— |
| Security | High |
Stopped `doctor` command from printing API‑key prefixes. Stopped `doctor` command from printing API‑key prefixes. Source: llm_adapter@2026-07-17 Confidence: high |
— |
| Refactor | Low |
Restored required UI and documentation assets to the package allowlist. Restored required UI and documentation assets to the package allowlist. Source: llm_adapter@2026-07-17 Confidence: high |
— |
Full changelog
Security and packaging
- Replaced permissive npm packaging with an explicit runtime-file allowlist.
- Added tracked-file and final-tarball checks for environment files, runtime config, logs, sessions, databases, key material, and development worktrees.
- Added the same checks to CI and
prepublishOnly. - Removed provider-shaped tokens from tracked visualization assets.
- Stopped
doctorfrom printing API-key prefixes. - Restored required UI and documentation assets to the package allowlist.
Verification on the release commit: CI passes; tracked credential scan passes; the 309-file tarball contains no forbidden paths.
Distribution note: this GitHub release is published, but npm 2.5.4 is not yet available because registry authentication is not configured on the release machine. Use the GitHub source until the registry publication and old-version deprecation are completed.
Security Fixes
- Removed provider‑shaped tokens from tracked visualization assets
- Stopped `doctor` from printing API‑key prefixes
- Restored required UI and documentation assets to the package allowlist
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
About AliceLJY/recallnest
Persistent memory MCP server for AI coding agents (Claude Code, Codex, Gemini CLI). Hybrid retrieval (vector + BM25), cross-encoder reranking, knowledge graph with PPR traversal, session checkpoint/resume, and multi-scope isolation. Local-first with LanceDB + SQLite, zero external dependencies.
Related context
Related tools
Beta — feedback welcome: [email protected]