Deepbom

Latest version: v1.96.9

Safety actively analyzes 1006753 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

1.96.9

- Added `deepbom mcp`, a stdio Model Context Protocol server exposing
`deepbom_capabilities`, `deepbom_audit`, and `deepbom_diff`. It is a transport
rather than an analysis command: it declares no output contract of its own,
answers every call by re-entering this CLI in a child process so the JSON-RPC
stream never shares stdout with an evidence document, and rejects undeclared
tool arguments. Its tool descriptions carry the finding-kind distinction and
the static-evidence boundary, and `scripts/check-mcp-server.mjs` rejects a
version that drops either. Source and installed-channel checks execute a real
ONNX audit through the transport, and runtime validation rejects undeclared or
conflicting arguments rather than silently ignoring them.
`deepbom.cli_capabilities.v1` now declares the transport under
`automation.mcp_stdio_server`.
- Published `llms.txt` at the domain root and an agent-facing skill at
`skills/deepbom/SKILL.md`, both stating that analysis is local and that no
hosted analysis endpoint exists. The discovery-metadata check asserts the
generated file keeps that boundary and the three finding kinds.
- Raised the measured source ceilings that the preceding web and agent work
exceeded: handwritten runtime to 11776 KiB, verification to 3328 KiB,
development tooling to 1408 KiB, and docs to 384 KiB.

1.96.8

- Added the bounded ONNX installation probe to every standalone engine and
Python wheel, and to the immutable Cargo engine matrix. Python and Cargo now
validate its declared path, size, and SHA-256 before executing the packaged
self-test; channel and published-engine smoke tests execute that probe.
- Made Cloudflare deployment fail closed when credentials are absent or
Wrangler uploads a version without activating a production target. Generated
deployment configuration now retains and validates the explicit
`deepbom.org` production routes.
- Raised only the measured 1.96.7 source ceilings: handwritten runtime by
64 KiB, verification by 18 KiB, and development tooling by 24 KiB. The same
source-budget gate now runs as part of local release validation, preventing
a clean local release record from diverging from the Cloudflare deployment
preflight. The generated public-source provenance manifest is excluded from
handwritten development-source accounting in both repository layouts. The
web workflow now installs its pinned public WASM build toolchain whenever a
deployable artifact is built; private-module smoke remains independently
conditional.

1.96.7

- Kept the Cloudflare deployment preflight browser-free by separating the
conversion-receipt module, IR, CLI, and tamper checks from the browser
binding exercised by Full Quality. This preserves the bounded deployment
gate without downloading Chromium into the release path.
- Added the packaged CLI self-test fixture to the exact public member
allowlist and bound its source bytes, packaged bytes, and release-manifest
SHA-256. This closes the six-platform package-boundary failure without
weakening the public/private distribution boundary.

1.96.6

- Reworked the website's first-use path around one local artifact or verified
example, then presents the shared Artifact Evidence IR as artifact defects,
cautions, evidence gaps, coverage, and direct next actions. Browser-local
Review HTML, Evidence JSON, and Evidence Package exports no longer require an
account.
- Added concise regulatory, quality, and engineering evaluation briefs while
keeping licensed standards text out of the distribution. Public product
surfaces and generated BOMs use stable CycloneDX 1.7 only.
- Added real frontend code splitting and interaction-loaded format analyzers,
report code, and TFLite WebAssembly. Corrected bundled Worker URLs so source
and deployed builds retain the same isolated analysis paths.
- Changed the CLI default to a bounded human review summary and added explicit
section and JSON Pointer selection, defect-only gating, installation
self-test, rule explanations, and categorized deployment-delta impact.
- Fixed npm and npx TFLite runtime asset discovery by resolving package assets
from the installed CLI module rather than the unresolved executable symlink.
- Separated learned, quantization, control, and unresolved constants so shape,
axis, index, and Slice sentinel values cannot contaminate learned-weight
magnitude or sparsity statistics. Constant-wide numerical integrity remains
independently assessed.
- Extended browser, installed-channel, public-boundary, mobile, theme, and
service-worker contracts for the new onboarding and output semantics. The
bounded deployment preflight now executes 84 checks with argument-safe test
dispatch.

1.96.5

- Moved every heavyweight TFLite WebAssembly analysis call behind one isolated
Worker RPC boundary, including target/frontier, redesign, influence,
calibration, histogram, landscape, tomography, and Haar analysis paths.
- Moved GGUF, SafeTensors, Core ML, and package range analysis to the same
file-scoped metadata Worker while preserving package-relative paths,
progress events, inactivity termination, and clean retry behavior.
- Added a static main-thread WASM boundary gate, Worker RPC contract checks,
and a reproducible JavaScript screening benchmark for the only prospective
streaming WASM candidates: incremental hashing and large payload decoding.
Independent JavaScript validators remain authoritative cross-checks.
- Fixed stale Artifact IR consumer views after protected selector or provider
evidence is merged, and kept the mobile Kernel Inspector controls and
selector decision ledger in the first visible panel region.
- Raised only the measured ceilings needed by the separately modularized
Worker protocol, RPC facade, enforcement checks, benchmark, and execution-
boundary documentation. Generated data, corpus, native tooling, private
source, and individual runtime-file ceilings are unchanged.

1.96.4

- Replaced the mutable CycloneDX 2.0 preview pins with a hash-verified draft
profile registry spanning specification PRs 990, 1067, 1075 and property
taxonomy PR 175. Incompatible or unresolved draft combinations now emit a
status record and refuse 2.0 BOM export; stable CycloneDX 1.7 remains the
default export.
- Added an RFC 9535 Perspective evaluator for Web and CLI that records exact
match counts and JSON Pointers while distinguishing zero, empty, multiple,
and type-mismatched results. Reference projection is explicit and
`relevance: required` remains unclassified until its normative cardinality
semantics are resolved.
- Added `deepbom.conversion_receipt.v1` for hash-only source checkpoint,
converter invocation, environment manifest, and deployment output lineage.
The output hash/format binding is observed while converter and source claims
remain `DECLARED_UNVERIFIED`; executable `.pt`, `.pth`, and `.h5` inputs are
never deserialized.
- Advanced Artifact IR method v2 to 2.2.0 so the same conversion lineage is
conserved through Web, CLI, evidence envelope, graph export, and CycloneDX.
Added tamper, cross-artifact, secret-bearing argument, and cross-surface
regression checks.
- Added bounded recovery for transient Engineering, regulatory, and raw-report
formatter module fetches, and corrected Evidence Package membership checks
so the non-BOM CycloneDX 2.0 draft-status record is not mistaken for a
`.cdx.json` document.

Page 1 of 3

© 2026 Safety CLI Cybersecurity Inc. All Rights Reserved.