For web application authors
Prepare HTML applications, widgets, demos, kiosks and client deliveries without turning every build into a separate command-line project.
Meet MLDarkMatter: a browser-based studio for JavaScript hardening, HTML packaging and evidence-led delivery. Explore every control, the technical workflow and the tools that make the result inspectable.
Self-contained English guide. Put it beside MLDarkMatter-v10.4.2.html to use the launch buttons.
Try a feature name such as “streaming”, a setting such as “optRuntimeSafety”, or clear the search.
MLDarkMatter is a browser-based HTML and JavaScript hardening, packaging and delivery-inspection studio.
Use it to make client-side JavaScript harder to read, prepare compact or password-gated script payloads, inspect the transformations actually applied, and assemble a traceable delivery. The browser application handles the local build workflow; companion tools handle signing keys, publisher trust and publication.
Prepare HTML applications, widgets, demos, kiosks and client deliveries without turning every build into a separate command-line project.
Inspect source risks, syntax, effective runtime policies, output metrics, startup observations and delivery authenticity as separate forms of evidence.
Produce standalone or split output, retain build history, export reports and manifests, and connect an external signing and trust-publication workflow.
An illustrative local HTML application in the editor, with the configuration area and an isolated preview. The source itself is not translated when the interface language changes.
The feature set includes editable source views, project assembly, deployment profiles, transformation presets, an option inspector, a conflict detector, large-file preflight, runtime preservation, diagnostics, loader skins, Mission Control, Explain my build, A/B and multi-configuration tools, Time Machine, a recipe library, visual reports, signing verification, plugins, a customizable dashboard and launch automation.
Implementation reference · README.md · src/app-core.js · docs/V10.4.2-RUNTIME-PRESERVATION.md
Start with the original source and keep the runtime compatibility controls enabled while establishing a working result.
| Edition or component | What it provides | What it needs |
|---|---|---|
| Standard HTML application | The complete interface and local pipeline. Attempts to load the pinned full obfuscator and HTML minifier. | A suitable browser; network access for those external engines. Inspect the actual engine reported for the build. |
| Offline HTML application | Embedded editor, ZIP support, AST tools and native source-preserving packaging. Compression and optional AES remain distinct pipeline capabilities. | No CDN engine fetch. It does not apply the full JavaScript obfuscation of the external engine. |
| Companion source package | Canonical sources, build tools, signing and trust utilities, test workflows and technical documentation. | Node.js and/or Python for the selected tool; TypeScript for changing canonical .ts modules; browser runtimes for browser checks. |
The guide itself is self-contained: screenshots, palettes, styles and interactive reference tools are embedded. External credit/reference links are optional navigation. The standard application and a protected application may still need their own network resources.
Implementation reference · README.md · src/app-core.js
Five input surfaces cover a single document, direct code and a small collection of local project files.
| Input | Workflow | Important behavior |
|---|---|---|
| File | Drag and drop or choose a .html/.htm document. | File name, byte size and large-file state are tracked. Large local files can take the streaming/preflight route. |
| HTML | Paste and edit a complete page in the syntax-highlighted editor. | Line numbers, character and size counts, caret position, diagnostics, formatting, undo and redo assist editing. |
| JS | Paste JavaScript on its own. | MLDarkMatter wraps it in a minimal HTML document for processing and preview. This is not a native executable packager. |
| URL | Fetch an HTML source by address. | Retrieval depends on browser permissions and CORS. The base URL is important for relative resources. Requests have a timeout. |
| Project | Choose a folder or several related HTML/CSS/JS/asset files. | Select the HTML entry, assemble supported local dependencies and inspect unresolved references. |
Prism highlighting for HTML, JavaScript and CSS; synchronized gutters; line/column and byte counts; diagnostics; 80-snapshot undo/redo stacks; Tab insertion and a basic HTML formatting action.
Framework-pattern detection covers React, Vue, Angular, jQuery, Svelte, Alpine, Lit, Web Components, compiled TypeScript and Webpack/Babel signatures. These are indicators, not a complete dependency graph.
Source scans can flag suspicious credentials, storage patterns, eval/new Function, insecure resource addresses, innerHTML and document.write. Existing-obfuscation detection warns about possible repeated transformation.
Built-in examples cover Basic HTML5, a React mini application, jQuery, a counter and Fetch API. The examples are source templates rather than application features: some deliberately depend on an external CDN or API. Pasting from the clipboard is available when the browser grants clipboard access.
Implementation reference · src/index.html · src/app-core.js · vendor/manifest.json
Project mode adds file selection and dependency inspection around the single-HTML build workflow.
A four-file documentation example loaded through the actual project importer. The HTML entry and local CSS/JavaScript dependencies remain visible for inspection.
Choose the entry HTML document, search the file inventory, and include or exclude individual files. The active HTML entry is protected against exclusion.
Eligible local classic scripts and linked styles are integrated; supported local assets and CSS URL references can be converted to data URLs. The interface reports unresolved resources instead of pretending they are bundled.
Export a JSON inventory using mldarkmatter-project/1. The manifest records the project assembly context; it is distinct from the signed delivery manifest.
Implementation reference · src/app-core.js: handleProjectFiles / rebuildProjectHtml / exportProjectManifest
Deployment profiles, transformation presets and saved recipes are complementary tools rather than interchangeable security guarantees.
| Deployment profile | Intended starting point | Notable configured direction |
|---|---|---|
Landing landing | A relatively simple landing page. | Compact output and string protection with conservative extra features. |
SPA spa | An interactive single-page application. | Balanced transforms, integrity and execution checks. |
Widget widget | An embeddable component. | Traceability and AES/integrity options; validate integration points carefully. |
Client client | A traceable client handover. | Stronger requested transforms plus AES and a build marker; do not assume execution checks are enabled by every profile. |
Demo demo | A demonstration build. | A light transformation path with a trace marker. |
Internal internal | An internal working build. | Minimal transformation pressure for easier inspection. |
| Preset | Requested control-flow / dead-code / string thresholds | Role |
|---|---|---|
Light light | 0.00 / 0.00 / 0.50 | A first functional baseline with low transformation pressure. |
Balanced balanced | 0.50 / 0.20 / 0.75 | A middle ground before measuring the result. |
Aggressive aggressive | 0.75 / 0.40 / 0.85 | More costly requested transforms; includes AES and integrity settings. |
Maximum max | 1.00 / 0.60 / 1.00 | The broadest requested set, including fragile integration options. It is not a performance preset. |
Reproducible reproducible | 0.50 / 0.20 / 0.75 | A deterministic-probe starting point; the separate probe also normalizes volatile metadata. |
The common build switches, profile/preset row, option search and expandable Expert groups. Search and the active-only filter reduce visual overload.
Implementation reference · src/app-core.js: DEPLOY_PROFILES / PRESETS / applyPreparedRuntimeSafety
Every checkbox in the v10.4.2 configuration is listed here. Costs below are qualitative guidance, not universal measurements.
optCompactReduces generated JavaScript size where the obfuscator can safely compact output.
Useful in almost every profile. It can make manual debugging harder because formatting is removed.
optCffMakes control flow harder to follow by restructuring execution paths.
Increase gradually. Combine with smoke tests; high thresholds can significantly inflate large applications.
optDceAdds unreachable or misleading blocks to increase reverse-engineering effort.
Use conservative thresholds. It compounds size growth with control-flow flattening.
optStrMoves literal strings into encoded lookup structures.
Best paired with string rotation/shuffle. Avoid expecting secrets to become cryptographically protected.
optRotateShuffles string-array layout to reduce obvious static patterns.
Only meaningful when string-array protection is enabled.
optSelfAdds self-defending logic intended to react to source reformatting.
Can interfere with formatters, instrumentation and some bundler transforms. Validate carefully.
optDebugAdds anti-debugging pressure around transformed code.
May interfere with legitimate debugging and automated tests. Prefer only for final delivery builds.
optConsoleSuppresses console output in protected scripts.
Runtime compatibility overrides suppression to preserve useful failures. Keep console is an additional explicit diagnostic control.
optEncryptEncrypts protected JavaScript payloads with AES-GCM and an external password.
AES-GCM encrypts compressed script payloads in v10.4.2. The password is not embedded in the output. Markup, styles and other unencrypted document material remain outside this protection.
optAntiDevtoolsAdds a lightweight runtime reaction to suspicious DevTools geometry changes.
It is a deterrent, not a security boundary. Avoid for accessibility-sensitive or embedded environments.
optIntegrityHashes each transformed script and verifies it before execution.
Integrity detects modification but does not prove publisher identity. Use signed manifests for authenticity.
optWatermarkEmbeds a build identifier for traceability and delivery correlation.
Use semantic version and build notes alongside the watermark for useful audit trails.
optFingerprintCreates a coarse local browser fingerprint for application-defined trace logic.
This creates a coarse local browser fingerprint for application-defined use; it does not provide a tracking service. Evaluate privacy implications before enabling it.
optCssObfRenames CSS classes and statically provable JavaScript class references.
Dynamic class generation can remain unresolved. Framework-heavy projects should use smoke tests and conservative profiles.
optLintChecks classic JavaScript syntax before expensive transformations.
Acorn validates extracted classic/module scripts during large-file preflight; other lint stages are deliberately conservative. A syntax pass is not a functional test.
optStaticScanFlags source patterns that deserve manual review before protection.
Findings are heuristic signals, not a vulnerability scanner verdict.
optLeakCheckSearches the generated result for identifiers or data that unexpectedly remain readable.
Recommended with sensitive-word filters and client delivery builds.
optNotifySends a native notification when a long build completes.
Only useful when browser notification permission has been granted.
optAutoSavePersists editor/session state locally to reduce accidental work loss.
Does not persist the AES password. Workspace export remains the portable backup path.
optRuntimeSafetyApplies a conservative per-script policy before obfuscation and preserves recognized function-source dependencies.
Enabled by default. Keeps console errors and integration names, reduces fragile transformations, and records requested/effective differences. Ambiguous reflection can lead to packing without obfuscator rewriting.
optRuntimeDiagnosticsMakes post-load errors observable, including errors triggered by a later user action.
Enabled by default. Observes JavaScript errors, rejected promises, Worker failures, console.error and CSP violations. The last recorded action is context, not proof that it caused an asynchronous failure.
optSmokeTestExecutes the generated output in a sandbox and captures runtime failures.
The current result means startup was observed under the test conditions. It does not prove that every button, delayed task, audio subsystem or network flow works. Isolation can change application behavior.
optStreamLargeProcesses very large local files without holding two full source copies plus a complete DOM.
Streaming avoids a complete DOM route above the threshold, and disables or reduces whole-document CSS rewriting, external inlining, global HTML minification and some global analysis. AST work on each large script still consumes memory.
optStreamOutputStreams generated output directly to File System Access targets through a MessagePort.
Best for large builds. Blob download remains the fallback when the browser API is unavailable.
optRenameGlobalsAllows obfuscation to rename global identifiers for stronger name hiding.
Can break frameworks, plugins and external integration points. Reserve known globals or avoid for third-party-heavy apps.
optNumbersRewrites numeric literals into less direct expressions.
Primarily raises reading effort; it should not be treated as a security control.
optSplitStringsBreaks literal strings into smaller fragments before reconstruction.
Use selectively with string-array protection; it can bloat string-heavy applications.
optUnicodeEscapes characters in transformed strings to make plain-text inspection less direct.
Improves opacity, not confidentiality. Compression can offset some size growth.
optInlineExtAttempts to fetch eligible external classic scripts and integrate them before protection.
Modules, async and defer scripts are intentionally preserved to avoid semantic breakage.
optObfModulesAllows ES module bodies to enter the obfuscation path.
Module imports, top-level await and browser execution semantics require careful validation.
optKeepConsolePreserves console methods even when console suppression is otherwise enabled.
Useful for staged or diagnostic builds; disable for quieter production output.
optMinifyHtmlReduces serialized HTML whitespace and redundant syntax.
Automatically disabled for large-file streaming paths that avoid full-DOM materialization.
optAdaptiveCompressCompares available compression formats and keeps the smallest payload.
Useful for standalone delivery; browser decompression support determines runtime portability.
optDetectObfWarns when the source already looks transformed or obfuscated.
A warning is not proof. Continue only when double-obfuscation is intentional.
optStrictCspInjects a nonce-based Content Security Policy around generated loader scripts.
The optional script policy can block inline event handlers and eval-style code. Inline visual styles remain intentionally permitted in the compatibility mode. Do not describe it as a universally strict policy for every resource.
The built-in inspector explains benefit, output-size impact, performance cost, compatibility risk and interactions, and can locate or toggle the associated control.
Implementation reference · src/app-core.js: OPTION_INSIGHTS · src/index.html · src/ts/runtime-safety.ts
The document-aware preparation stage and the compute-heavy transformation stage have different responsibilities.
| Stage | Responsibilities | Boundary |
|---|---|---|
| Main browser thread | UI orchestration, DOMParser/CSSOM operations, Acorn-based source reasoning, input preparation, File System Access destination handling. | Moving heavy transforms to a Worker does not mean every preparatory stage is off the main thread. |
| Main build Worker | Obfuscation, compression, optional AES-GCM, script hashes, loader construction and output transmission. | A synchronous obfuscator call can still be expensive inside the Worker. Cancellation includes terminating/resetting a Worker when necessary. |
| Runtime loader | Recover payloads, verify configured hashes, insert scripts at recorded locations, expose progress and bounded diagnostics. | Asynchronous unpacking is not identical to the HTML parser’s original blocking behavior. |
| Companion signing tools | Sign manifests, operate a trust-store, interact with a remote signer and publish trust evidence. | Private signing keys stay outside the browser/editor workflow. |
CSS class renaming uses CSSOM selectors and Acorn analysis of JavaScript references. Supported reference forms include querySelector(All), getElementsByClassName, classList operations, className and setAttribute("class", …). The static evaluator can resolve unambiguous constants, concatenation, static template strings, arrays joined into strings and small pure helper calls across function boundaries. It abandons mutation, shadowing, side effects and ambiguous values rather than executing the source to guess an answer.
Structured hook rules can remove, replace or rename calls and replace string literals. A where condition only applies when argument values are demonstrable, including through supported pure helpers. The transformed JavaScript is parsed again before acceptance.
[
{
"kind": "call",
"callee": "feature",
"where": { "arg": 0, "equals": "legacy" },
"action": "rename",
"to": "featureV2"
},
{ "kind": "string", "value": "Draft", "replacement": "Release" }
]Text/regular-expression hooks remain available with find, replacement and flags fields, plus code injection before or after each script. Sensitive-word substitutions use a configurable prefix and numbered replacements. These are purposeful source edits, not a secret vault: verify the effect on strings, identifiers and application contracts. In compatible mode, combinations that would silently change frozen Worker-function sources are rejected.
Implementation reference · src/css-ast.js · src/app-core.js · src/ts/runtime-safety.ts · src/runtime-loader.js
v10.4.2 adds a per-script compatibility policy and local diagnostics for failures that happen after startup.
The runtime panel records adaptations for each script. This example explicitly reduces self-defending code and console suppression instead of claiming the preset was applied unchanged.
Scripts of at least 512 KiB of JavaScript text, and recognized audio/numerical patterns, receive reduced exposure to costly transformations in compatible mode. Expensive transformations can make an otherwise valid interactive application impractically slow.
Recognized immutable functionName.toString() uses can be replaced by the original function source text before obfuscation. This helps self-contained functions used to construct Workers or other execution contexts.
Reassignment, shadowing or detected reflection changes prevent an unsafe inferred rewrite. Known ambiguous cases may be packed without obfuscator rewriting; the effective policy explains the decision.
JavaScript errors, unhandled promise rejections, Worker errors, console.error() calls from caught failures, CSP violations and the most recently observed user action provide context when an application button appears silent. The in-page window.__MLDM_RUNTIME__ summary is bounded. Loader events include mldm:ready, mldm:failed, mldm:password-required, mldm:issue and mldm:progress.
Small sources can use the live preview. A protected result is loaded deliberately with Load isolated preview; large local previews are checked against a 64 MiB materialization limit. Full-result and side-by-side views are also available. The safe preview blocks network access by default; the network permission toggle is explicit. The AES password form lives inside the protected page rather than relying on a native modal prompt.
The loader no longer depends on animation frames to advance between scripts, which avoids an essential startup step waiting for a hidden frame’s visual refresh. Isolated previews still omit allow-same-origin: storage, AudioWorklet, WebGPU, secure-context APIs and network resolution can differ from the downloaded application on its final origin.
Implementation reference · docs/V10.4.2-RUNTIME-PRESERVATION.md · src/ts/runtime-safety.ts · src/runtime-loader.js
A dedicated preflight validates extraction and syntax before a large monolithic application enters expensive transforms.
The actual preflight identifies two executable scripts, validates both, reports the largest script and records Unicode case-expansion occurrences without using transformed-text offsets.
| Capability | Behavior in v10.4.2 |
|---|---|
| Activation | Large local-file streaming is enabled by default; the default threshold is 8 MiB. The configuration exposes the threshold. |
| Stable tag offsets | HTML tag names use ASCII-only case matching. Source positions are never taken from a Unicode-lowercased copy with a different length. |
| Incremental boundaries | Quoted > characters in tags, mixed tag case, split tags, UTF-8 boundaries and surrogate pairs receive dedicated handling. |
| HTML contexts | The scanner recognizes comments, raw-text elements, inert templates, and escaped/double-escaped script states. It is not advertised as a universal replacement for every HTML5 parser edge case. |
| UTF-8 policy | Malformed UTF-8 is rejected instead of silently inserting replacement characters. A legacy-encoded document should be converted deliberately before processing. |
| Preflight evidence | Script count, classic/module classification, source size, largest-script size, boundary diagnostics and per-script syntax results. |
| Bounded recovery | If extraction or syntax appears inconsistent, a DOMParser retry is permitted up to 64 MiB and scripts are checked again. Larger sources are not silently rematerialized. |
| Memory trade-offs | Whole-document CSS rewriting, external inlining, global HTML minification and some global scans are reduced or disabled on the streaming route. |
| Retention reductions | Consumed Worker source text is released; redundant source/prepared-tree transfers are avoided; compression candidates are compared sequentially; output text windows do not split surrogate pairs. |
Implementation reference · src/ts/streaming.ts · src/ts/output-stream.ts · docs/V10.4.2-RUNTIME-PRESERVATION.md
Choose packaging, appearance and transport separately from the transformation policy.
| Output path | Contents | Trade-off |
|---|---|---|
| Standalone HTML | One protected HTML document with loader configuration and script payloads. | Convenient distribution; external resources in the original application are not magically removed. |
| Split HTML + JavaScript | The HTML document and app.protected.js, downloadable together in a ZIP. | Keep both files together and use a suitable HTTP(S) origin for module/network-dependent applications. |
| Stream output to disk | A file or directory selected before the build; Worker chunks are written through a MessagePort to FileSystemWritableFileStream. | Avoids the final giant concatenation/Blob on this path. Some previews and structural metrics are unavailable when output text is intentionally not retained. |
| Portable bundle | Application file(s), manifest.json, README.md and report.html. | Creating a bundle does not itself sign it. Complete signing and trust publication externally. |
| Multi-watermark archive | Multiple deliveries from one source, each carrying a supplied build identifier. | This creates client/build variants of one source; it is not a general multi-project build queue. |
Neutral dual-ring progress.
minimalMonospace and phosphor-style accents.
terminalA technical grid with luminous accents.
cyberTranslucent panel treatment.
glassRestrained scan-line styling.
crtEngineering-grid character.
blueprintA central ring and pulse field.
pulseA radial dark-matter vignette.
eclipseThese cards are palette/style illustrations, not repeated application screenshots. The selected application loader profile is embedded in standalone, split and streamed output. Loader title and accent colors are configurable; an interface theme and a delivered loader skin are separate choices.
Adaptive compression tries the supported gzip, deflate and deflate-raw paths and keeps the shortest encoded representation. Without adaptive selection, the pipeline has a gzip path. Script text is compressed before AES-GCM encryption in v10.4.2. PBKDF2 uses SHA-256 to derive a 256-bit AES key, with a random 16-byte salt and 12-byte GCM IV; the UI exposes the iteration count. The password must be retained and delivered separately.
Implementation reference · src/app-core.js: loader / compression / bundle · src/ts/output-stream.ts · src/runtime-loader.js
The inspection tools turn a build into a sequence of observable decisions rather than one opaque progress bar.
Open the live pipeline view from the top bar or console. Six phase cards, current stage, percentage, event log, elapsed time, input/output metrics, engine identity and script count provide a build overview. Phase labels describe the actual reported stage; the progress percentage is not a claim of line-by-line CPU measurement.
A completed documentation build, with its phase path and event log. The engine is identified as offline-native; the small fixture is not a performance benchmark.
The post-build summary gathers scripts, module counts, encryption, active options, engine, seed, source/final size, time, index, findings, syntax issues, external inlining failures and startup observations. It exposes transformations and limitations without requiring the user to interpret the full source diff.
The factual summary for the same demonstration delivery. A small input can grow after packaging because the runtime loader has a fixed overhead.
The smart comparator groups source/final byte counts, payload count, scripts, external scripts, CSS class counts, renamed classes, readable named functions, sensitive substitutions, hook changes and inlining errors. It links to the traditional textual diff. The diff uses a Patience-style approach, a Worker for larger comparisons and bounded fallback behavior; whitespace can be ignored.
Structural counts complement a textual diff. Payload records and injected loader scripts are different concepts, so script-tag counts need interpretation.
The per-script analysis table lists source, transformed and encoded/compressed sizes, classic/module classification and the selected algorithm. The timeline and log retain stage durations and timestamped messages. Copying the log, exporting a report and saving a manifest support support requests and handover documentation.
Implementation reference · src/app-core.js: Mission / Explain / Smart comparison / Benchmark · src/diff-worker.js
Use controlled experiments for configuration decisions and a local history for traceable iterations.
A/B selects two deployment configurations. The laboratory runs at least two selected profiles sequentially against one source, uses a fixed seed for comparable transformation inputs, and shows index, output size and elapsed build time. It highlights leaders per metric rather than inventing a single best result. Profiles that request AES depend on WebCrypto availability; always inspect the actual engine and effective context.
Three genuine native-packaging runs on the small Orbit example. Similar output sizes are expected when the full obfuscator is not used; these results are illustrative, not product speed claims.
Time Machine presents saved builds along a selectable timeline, with date range, size, index, version, build ID and notes. The current build can be shown even while persistence is unavailable or unfinished. History supports filtering, selection, deletion, metadata export, comparisons and reloading retained output. Multi-build views and statistics summarize size/gain evolution, counts, versions and recorded leak flags.
The current documentation build appears with its trace identifier and note. Persistent history depends on the browser storage context.
Implementation reference · src/app-core.js: processForAB / runLab / saveBuild / renderTimeMachine
Conflict detection, a readiness view, reproducibility probes and a delivery report serve different review tasks.
Explicit rules consider framework patterns, input size, streaming state and settings. Examples include global renaming with a framework, dynamic classes with CSS renaming, anti-debugging with execution checks, external inlining with input streaming, and high transformation thresholds. Each finding carries a high, medium or informational level, an explanation and a suggested mitigation. The detector does not silently reconfigure the build.
An intentionally demanding configuration reveals interactions before processing. The mitigations are review guidance, not automatic changes.
Four independent axes separate Functionality, Compatibility, Authenticity and Confidentiality. A startup observation is not a functional certification. A compatibility scan is not a test on every browser. A hash alone does not identify the publisher. No obvious plaintext finding does not prove confidentiality. Check the actual engine when interpreting older wording such as “obfuscation only”.
The screenshot keeps unverified authenticity distinct from startup and compatibility observations. It does not grant release authorization.
The readiness probe lists volatile inputs: random AES salt/IV, a fresh CSP nonce, mutable inlined network resources, a random seed, an automatically created watermark and multi-watermark variants. Apply reproducible settings to establish a fixed seed and build identifier and remove the probe’s known sources of nondeterminism. It then builds twice and compares output SHA-256 values.
The probe explains why the selected configuration is not yet suitable for a byte-identical comparison.
Export an autonomous delivery sheet with source/final size, gain, duration, hardening index, readiness evidence, transformation badges, provenance, available SHA-256 values, build ID and per-script metrics. Its visual fingerprint is a human-recognition aid, not a QR-based verification service and not a digital signature. A bundle includes this report alongside its manifest and README.
A real report export from the documentation fixture. Demonstration metrics and unavailable verification evidence should not be read as a performance result or signed publisher claim.
Implementation reference · src/app-core.js: conflicts / ship-readiness / reproducibility / report
The browser verifies publisher evidence; companion tools operate the signing and trust lifecycle.
The delivery manifest binds file names, byte sizes and SHA-256 values. A detached Ed25519 signature authenticates that manifest. In trust-store mode, the verifier also checks the public root, trust-store signature, policy, key status and relevant version constraints. Delivery files can be selected to check their contents, rather than checking only the manifest signature.
The genuine verification form accepts the manifest, detached signature, public trust material, optional root pin and delivery files. A legacy direct-public-key path is also available.
| Trust capability | What it adds |
|---|---|
| Root/signing-key separation | The root signs trust-store versions and transparency checkpoints; a manifest key signs delivery manifests. The remote service enforces purpose restrictions. |
| Rotation | Retire an old signer and introduce another public key without moving private material into the browser. |
| Revocation and policy | Key states include active, retired and revoked. Policy can require known keys, permit eligible historical retired signatures, and use hard or time-based revocation behavior. |
| Root pinning | A SHA-256 root fingerprint must arrive through a trusted channel. A pin delivered with an untrusted replacement root is not a trust anchor by itself. |
| Rollback resistance | CLI minimum-version requirements and a browser high-water mark per root detect older signed trust-store versions. Clearing local storage can remove the browser’s remembered high-water mark. |
| Public publication | Only the public root, public signer keys, signed registry and publication evidence belong in the public delivery directory. |
| Remote signing / HSM adapter | An authenticated service signs purpose-bound documents using configured keys. The command-HSM backend passes a document and key handle to an external HSM/KMS agent and verifies its returned signature. |
| Optional transparency | A hash-chained append-only JSONL publication log and an optional root-signed checkpoint help verify the published chain’s consistency. This is not a globally witnessed transparency service. |
| Tool | Purpose |
|---|---|
generate_signing_key.mjs | Generate a development/local signing key pair outside the client. |
sign_manifest.mjs | Create a detached signature for a manifest. |
verify_manifest.mjs | Verify a manifest against signature/public-key material. |
verify_delivery.mjs | Verify the signed manifest and its linked artifact contents. |
init_trust.mjs | Initialize a root-backed trust-store. |
rotate_signing_key.mjs / revoke_signing_key.mjs | Manage local trust lifecycle changes. |
remote_signing_service.mjs | Expose restricted public-key/sign operations with bearer authentication and role/purpose enforcement. |
remote_sign_manifest.mjs | Request a manifest signature without loading its private signing key on the build client. |
remote_trust_admin.mjs | Bootstrap, rotate or revoke trust entries through the remote root signer. |
publish_trust_store.mjs | Validate a supplied root pin and publish the public trust bundle; optionally append transparency evidence. |
verify_publication.mjs | Verify pinning, minimum version, registry signature, publication hashes and optional log/checkpoint evidence. |
The publishable output includes root-public-ed25519.pem, public signer keys, trust-store.json, trust-store.signature.json, root-pin.json and publication.json. An optional log checkpoint records chain size and head hash. Replicate trusted checkpoints through independent channels when conflicting views are a concern.
Implementation reference · src/ts/manifest-auth.ts · tools/ · docs/HSM-REMOTE-SIGNING.md · docs/TRUST-PUBLICATION.md
Reusable settings, fast navigation and visual explanations keep the feature set accessible.
Six cards provide Quick start, Recent builds, Favorite recipes, Trust & authenticity, Tools and Session. Reorder cards with the layout controls, hide those you do not need, and retain the arrangement locally. Shortcuts open files, projects, clipboard input, Mission Control, the laboratory, plugins, Theme Studio, delivery verification and readiness checks.
The six real dashboard cards. Recent builds and favorite recipes populate when those records are available in local storage.
Filter cards by search or category, mark favorites and apply a recipe. Built-in cards cover React/Vue SPA, Embedded widget, Client delivery, Offline kiosk, Legacy application and Commercial release. User recipes stored in IndexedDB join the same library. The configuration row also provides named save, import, export and deletion actions.
Six built-in recipe cards, with categories and favorite controls. A recipe is a starting configuration, not a promise of compatibility with every application of that category.
Presentation mode temporarily simplifies the interface around Import → Analyze → Protect → Verify → Deliver while using the same pipeline. Simple and Expert modes control how much configuration is exposed. The left rail, top-bar tools, command palette, searchable help, hover/focus tooltips, active-option filter, selectable themes and native keyboard controls provide multiple paths to the same operations.
Backup & workspace exports/imports configuration and can migrate recipes and historical build records in a ZIP. Local preference persistence and session recovery are separate from a portable backup. AES passwords and sensitive-word lists are excluded from configuration persistence/export paths intended to omit those values; source drafts and downloaded artifacts still deserve normal confidentiality handling.
Implementation reference · src/app-core.js: dashboard / recipes / presentation / workspace
These are the application’s actual v10.4.2 theme tokens. Choose a card to apply its palette to this guide.
Palette previews are live HTML swatches, not duplicated screenshots. Theme changes recolor this guide; the embedded screenshots remain faithful to the captured application.
| Theme role or guard | Implementation |
|---|---|
| Registered palettes | Obsidian, Aurora, Cobalt, Emerald, Crimson, Amber, Violet, Rose, Cyan, Graphite, Synthwave, Solarized, Arctic, Ivory, Mint Light and High Contrast. |
| Light variants | Arctic, Ivory and Mint Light are identified as light themes. |
| Primary/secondary text | The guard checks at least 7:1 for primary text against the base background and 4.5:1 for secondary text. |
| Accent checks | At least 3:1 for the primary accent against the base background and 4.5:1 for text on the primary accent. |
| Theme Studio | Edit 13 roles: four background levels, primary/secondary/muted text, three accents, and success/warning/error. Preview live, validate, apply, save, import or export JSON. |
| Reset behavior | The shipped Theme Studio reset action restores the Obsidian base palette. |
| Scope of the guard | It checks selected token pairs. It does not certify every translucent surface, hover combination, custom style or image in an application. |
Editable color roles, an immediate preview and explicit contrast ratios. Theme configuration affects presentation rather than the protected program’s behavior.
Implementation reference · src/themes.js · src/app-core.js: Theme Studio
Nineteen language choices coexist with technical identifiers, source editors and isolated content previews.
| Code | Language | Native label | Direction |
|---|---|---|---|
fr | French | Français | Left to right |
en | English | English | Left to right |
de | German | Deutsch | Left to right |
es | Spanish | Español | Left to right |
pt | Portuguese | Português | Left to right |
it | Italian | Italiano | Left to right |
da | Danish | Dansk | Left to right |
fi | Finnish | Suomi | Left to right |
is | Icelandic | Íslenska | Left to right |
no | Norwegian | Norsk | Left to right |
sv | Swedish | Svenska | Left to right |
nl | Dutch | Nederlands | Left to right |
ru | Russian | Русский | Left to right |
zh | Chinese | 中文 | Left to right |
ja | Japanese | 日本語 | Left to right |
ko | Korean | 한국어 | Left to right |
ar | Arabic | العربية | Right to left |
he | Hebrew | עברית | Right to left |
la | Classical Latin | Latina | Left to right |
The localization layer observes application UI changes and remembers original node text so language switching remains reversible. It avoids translating source-editor content and embedded application frames. Arabic and Hebrew use right-to-left interface direction. This presentation is English; the captured release may retain legacy wording in some application labels and explanatory strings.
| Shortcut | Action |
|---|---|
| F1 | Open integrated help. |
| Ctrl/Cmd + K | Open the command palette. |
| Ctrl/Cmd + Enter | Process the loaded source when idle. |
| Ctrl/Cmd + S | Download a retained result. |
| Ctrl/Cmd + H | Open build history. |
| Ctrl/Cmd + Alt + A | Open A/B comparison. |
| Ctrl/Cmd + Alt + M | Open multi-build comparison. |
| Ctrl/Cmd + Z / Y | Undo/redo in a source editor; Shift+Z is also a redo form. |
| Escape | Close modal surfaces and clear active preview frames. |
| ↑ / ↓, Tab | Recall commands and autocomplete in the internal console. |
The reversible Singularity effect can be toggled by the internal singularity command, its public API or the deliberate sequence ↑ ↑ ↓ ↓ ← → ← → B A. It changes presentation only, not files, options or pipeline results.
Implementation reference · src/i18n.js · src/i18n-expert.js · src/app-core.js: shortcuts / Singularity
Plugin API v1 accepts a structured manifest and executes each enabled plugin in a disposable Worker.
An installed sample build-marker plugin, with declared stage/permissions and enable, export and remove controls. Importing a plugin is separate from executing a build.
| Contract | Supported values or limits |
|---|---|
| Schema | mldarkmatter.plugin.v1 |
| Stages | source:before and result:after |
| Permissions | read-source, transform-source, read-result, transform-result |
| Identifier | 3–64 safe identifier characters. |
| Code | 1–120,000 characters. |
| Execution timeout | Default 900 ms, clamped to 100–2,000 ms. |
| Result bound | Output is rejected above the larger of three times input length or input length plus 1 MiB. |
| Execution order | Enabled plugins run sequentially for their selected stage; a transformation/error record is added to the build log. |
| Storage | IndexedDB with a bounded fallback when primary storage is unavailable; fallback retains up to 10 plugin records. |
{
"schema": "mldarkmatter.plugin.v1",
"id": "example.build-marker",
"name": "Build marker",
"version": "1.0.0",
"permissions": ["read-source", "transform-source"],
"stages": ["source:before"],
"timeoutMs": 900,
"code": "return input;"
}The Worker has no DOM, and the wrapper removes the common fetch, XMLHttpRequest, WebSocket, EventSource and importScripts entry points. The input/context contract, timeout and output limits constrain the extension stage. Import/export, activation, removal and a harmless sample are provided in the manager.
Implementation reference · src/app-core.js: normalizePlugin / runPluginSandbox / applyPluginStage
HTML applications receive URL parameters, not native operating-system argv. The integrated console is a command dispatcher, not a system shell.
The actual PowerShell-style command surface showing application status and registered values. This interface does not execute PowerShell or operating-system commands.
| Parameter | Value form | Meaning | Example value |
|---|---|---|---|
lang | code | Interface language. Select one of the 19 registered language codes. | fr |
theme | name | Initial palette. Select one of the 16 registered theme identifiers. | obsidian |
mode | simple|expert | Initial configuration exposure: simple or expert. | expert |
profile | name | Deployment profile: landing, spa, widget, client, demo or internal. | spa |
preset | name | Transformation preset: light, balanced, aggressive, max or reproducible. | balanced |
tab | file|html|js|url | Initial source tab. The startup catalogue advertises file, html, js and url; the Project workflow is also available in the application. | html |
source-url | URL | Fetch an HTML source from an allowed URL. The server must permit the request. Alias: url. | https://example.test/app.html |
source-data | base64|URI | Load embedded source prefixed with base64: or uri:. Base64 represents UTF-8 text. | base64:PCFET0NUWVBFIGh0bWw+ |
source-text | URI text | Load a URI-encoded HTML source string. | %3Ch1%3EHello%3C%2Fh1%3E |
file | path|URL | Try a source path or URL. This cannot grant silent access to an arbitrary local file on a recipient’s computer. | sample.html |
process | 0|1 | Start processing after the startup source is available. It does not bypass source, capability or password checks. | 1 |
output | standalone|split | Choose standalone or split output. | split |
preview-network | 0|1 | Enable or disable network access in the isolated live preview. | 0 |
stream-threshold | MB | Large-file threshold in MB. The startup handler clamps it to the supported 2–512 range. | 8 |
notify | 0|1 | Enable completion notifications when browser permission already exists. | 1 |
console | 0|1 | Open the internal startup/developer console after initialization. | 1 |
help | 0|1 | Open the complete startup help in the PowerShell-style console. Alias: ?. | 1 |
Parameters can be supplied in the query string or URL hash. Recognized hash parameters are processed after query parameters; unknown names are ignored. When both profile and preset are supplied, the preset is applied after the profile. An empty recognized flag is interpreted as enabled. The reserved configuration-sharing hash has its own handling.
./MLDarkMatter-v10.4.2.html?lang=en&theme=cobalt&mode=expert&preset=balanced
./MLDarkMatter-v10.4.2.html?help=1
./MLDarkMatter-v10.4.2.html?source-url=https%3A%2F%2Fexample.test%2Fapp.html&process=1Choose initial interface settings. This only prepares a relative link; it does not upload data or start a build.
| Command | Action |
|---|---|
help / clear | Show the console reference or clear its visible output. |
status | Report the current version, interface state and input/result availability. |
themes, langs, profiles, presets | List registered values. |
analyze | Run the source pre-analysis; this is distinct from a button inside a protected application. |
build / process | Start the normal processing workflow. |
dashboard, mission, lab | Open the dashboard, Mission Control or Laboratory. |
time / time-machine, history | Open the timeline or historical build list. |
ship, smart-compare, diff | Open readiness evidence, structural comparison or text comparison. |
verify | Open the manifest/signature verification interface. |
conflicts, reproducible, recipes | Open configuration conflicts, repeat-build checks or the Recipe Library. |
theme-studio, plugins | Open the color editor or plugin manager. |
presentation, singularity | Toggle the presentation workflow or the optional visual effect. |
project manifest | Print the loaded project manifest. |
profile <name>, preset <name> | Apply a deployment profile or transformation preset. |
theme <id>, lang <code> | Change the active palette or interface language. |
set lang=en, set theme=cobalt, set mode=expert | Apply supported interface settings through the console parser. |
Use the up/down arrow keys for command history and Tab for completion. The implementation bounds remembered commands to 60 entries. The command palette is a separate, searchable graphical entry point. Console commands do not expose a native shell, nor do they evaluate arbitrary expressions.
| API group | Exposed members |
|---|---|
| Identity and state | version, languages, themes, language, theme, premiumFeatures, startupOptions. |
| Interface and startup | setLanguage, setTheme, parseStartupOptions, applyStartupOptions, openStartupConsole. |
| Build inspection | openMissionControl, explainBuild, openLab, openTimeMachine, openShipCheck, openSmartCompare. |
| Configuration and appearance | inspectOption, detectConflicts, openThemeStudio, setPresentationMode, setSingularityMode, openReproducible, openRecipeLibrary, openDashboard. |
| Projects and plugins | projectManifest, loadProjectFiles, openPluginManager, plugins.list, plugins.register, plugins.remove. |
window.MLDarkMatter.setLanguage('en');
window.MLDarkMatter.setTheme('cobalt');
window.MLDarkMatter.inspectOption('optRuntimeSafety');
window.MLDarkMatter.openMissionControl();Implementation reference · src/launch-options.js · src/app-core.js: executeConsoleCommand / public API
The 35 switches are documented above. These additional fields define numeric thresholds, source edits, delivery metadata and output appearance.
| Field or group | Accepted content / behavior |
|---|---|
| Control flow threshold | thCff: 0–1, step 0.05; default 0.50. Used only when the corresponding transformation is enabled and retained by the effective policy. |
| Dead-code threshold | thDce: 0–1, step 0.05; default 0.20. |
| String-array threshold | thStr: 0–1, step 0.05; default 0.75. |
| Password derivation work | thPbkdf2: 50,000–500,000 iterations, step 50,000; default 150,000. This is a configurable implementation range, not a recommendation for every deployment. |
| Text hook | hookPreFind, hookPreReplace, hookPreFlags (default g): a regular-expression search/replacement before script processing. Invalid expressions must be diagnosed. |
| Structured hook rules | hookStructuredRules: JSON rules for supported AST call/literal transformations and optional argument conditions. |
| Code insertion | injectBefore and injectAfter: JavaScript placed around each processed script. These can change scope, initialization and correctness. |
| Sensitive-word substitution | sensitiveWords: one term per line. sensitivePrefix: replacement prefix, default _x. A substitution is not a guarantee that secrets have been removed from every data path. |
| Reserved names | reservedNames: newline/comma-separated entries passed to the obfuscator’s reserved-name mechanism. Pattern metacharacters have meaning; take care with names such as $. |
| Streaming threshold | streamThresholdMb: large-file input threshold, default 8. The startup parser supports the 2–512 MB range. |
| Randomization seed | seed: a fixed numeric value or an automatically chosen value when blank. A repeatable transform seed is not an encryption key. |
| Build identity | watermark: Build ID; buildVersion: version label; buildTags: comma-separated tags; buildNote: human-readable note. |
| Multiple identities | multiWatermarkList: one target identity per line for multiple variants of the same source. |
| Encryption password | password: supplied at build time or generated when blank. The generated payload does not include the password. |
| Deployment checks | domainLock: comma-separated domains; expiresAt: expiry date used by a browser-side check. Neither is server-enforced licensing. |
| Loader appearance | loaderTitle: waiting text; loaderProfile: one of eight skins; the loader color selector supplies an accent pair independently of the studio palette. |
| Output format | outFormat: standalone or split. Disk-streaming controls alter where output is written, subject to API availability. |
| Configuration management | Named recipes, profile/preset actions, reset, JSON import/export, active-option count/filter and option search manage the same configuration surface. |
| Layer | v10.4.2 implementation |
|---|---|
| Browser UI | HTML/CSS/JavaScript, responsive app shell, SVG controls, modal tools, keyboard shortcuts, syntax highlighting and client-side storage. |
| HTML preparation | DOMParser for the normal path, plus a streaming HTML scanner for large local files. No DOMParser is assumed inside the processing Worker. |
| JavaScript analysis | Acorn 8.15.0, AST traversal, syntax validation, conservative value propagation and inter-procedural checks for supported pure helpers. |
| CSS analysis | Browser CSSOM plus JavaScript AST inspection. Unproven dynamic classes are not safely inferable by merely guessing names. |
| Full transformation engine | Optional javascript-obfuscator 4.1.1 in the standard Worker path. Its costs and supported syntax remain relevant even after valid extraction. |
| HTML minifier | Optional html-minifier 4.0.0 when available; full-document minification is not applied on the memory-constrained streaming route. |
| Compression / cryptography | CompressionStream / DecompressionStream; Web Crypto SHA-256, PBKDF2-SHA-256, AES-256-GCM and supported Ed25519 verification paths. |
| Storage and exchange | IndexedDB for local records, guarded localStorage preferences, Blob URLs, JSZip archives and File System Access where available. |
| Typed pipeline modules | Seven canonical TypeScript modules: contracts-runtime, manifest-auth, output-stream, runtime-safety, script-schedule, security and streaming. The whole project has not been migrated to TypeScript. |
| Distribution build | A Python builder composes source modules and embedded vendor files into standard/offline HTML distributions. Generated TypeScript runtime files are consumed by the builder. |
| Optional developer bundler | esbuild development/watch path. The package declares esbuild ^0.25.0 and TypeScript ^5.8.0; these are dependency ranges, not claims that those exact versions are embedded in the HTML. |
| Companion services | Node.js command-line tools for manifest signatures, delivery checks, trust administration, remote signing and publication. These are not a browser-hosted HSM. |
| Automated checking | Node/Python suites, TypeScript checks and a strict Playwright matrix configured for Chromium, Firefox and WebKit on pre-provisioned multi-OS runners. |
| Capability | Practical consequence |
|---|---|
| Worker, Blob and MessageChannel | Needed by processing, isolated extension work and the acknowledged output path. Browser policies may prohibit some worker/URL forms. |
| Compression streams | Needed for the native compressed payload path; supported algorithm variants are capability-dependent. |
| Web Crypto in the current context | Needed for cryptographic operations. Feature presence and origin policy must be checked where the app actually runs. |
| Ed25519 | The browser verification path needs implementation support. Companion Node tools offer an external verification workflow. |
| File System Access pickers | Optional. Direct-to-disk output is used only after explicit destination selection; other browsers use downloadable artifacts instead. |
| IndexedDB / localStorage | May be blocked, quota-limited or unavailable in private/opaque contexts. A successful build is not the same as successful persistence. |
| Network and origin policy | Source retrieval, external scripts, service workers, module imports and protected-app APIs follow their own CORS, CSP and origin requirements. |
| Clipboard / notifications | Depend on browser permission, context and user interaction. The application does not gain these permissions simply because an option is enabled. |
python3 build/build_dist.py
npm run build:ts
npm run typecheck
npm run build:esbuild
npm run dev
npm run test:matrix:strictImplementation reference · package.json · build/build_dist.py · src/ts/ · src/types/contracts.ts · docs/V10.4.2-RUNTIME-PRESERVATION.md
A practical decision guide for the failure modes that matter when distributing an interactive HTML application.
Keep Runtime compatibility and Runtime diagnostics enabled, rebuild from the original source and reproduce the action on the intended deployment origin. Inspect errors, rejected promises, Worker failures and CSP violations. A startup-only smoke check cannot exercise every later click. The last recorded action is context, not proof of causation.
Compare the effective per-script settings, not only the preset name. Large numeric loops and audio routines are particularly sensitive to added control-flow and numeric-expression work. Use the compatible policy, compare profiles and verify interaction latency. Password derivation and payload decompression also add startup work.
Choose Load isolated preview for the retained result. Review the large-preview limit, network setting and the inline AES unlock form. An opaque sandbox has different storage and secure-context conditions from the delivered page. Do not remove isolation merely to hide the difference.
Use the Unicode-safe scanner and preflight evidence in this release. It preserves source offsets and validates extracted JavaScript before obfuscation. A bounded safe-parser retry is available up to 64 MiB; the obfuscator’s own syntax support remains a separate stage.
That is expected for the offline-native engine: it preserves source while packaging, compressing and optionally encrypting script payloads. Select the standard engine and confirm its reported availability when full obfuscation is required.
Keep the split HTML and app.protected.js together, along with any still-external dependencies. Test through the intended server when modules or other origin-sensitive features need it.
Inspect unresolved references and import warnings. Small-project assembly is not a general module/dependency bundler. Runtime-created URLs, workers, module graphs and external assets may require a proper project build or deployment layout.
Review the explicit text/accent contrast checks and change the offending roles. Passing the palette guard is useful but does not test every surface or state. Use High Contrast as a known starting point.
Verify the trusted root pin, signed trust-store, version floor, key state and applicability of the revocation policy. A valid signature from an untrusted or revoked key is not an accepted publisher identity.
The picker requires an available API, an allowed context and a user-selected destination. Use the ordinary download path when unsupported. Cancellation or write failure should remain distinct from a completed delivery.
A meaningful comparison requires two completed builds and two actual, non-empty SHA-256 values. AES randomness, nonce generation, fetched content and build metadata can legitimately differ. Do not interpret two missing hashes as evidence of reproducibility.
The release offers 19 language packs, but some legacy/dynamic labels remain inconsistent. Technical names and source code should stay unchanged. This guide is written in English and preserves the real screenshots rather than relabelling them.
No private key is needed in the browser distribution. Keep signing outside the application; provision and authorize the companion signer separately. A public key is publishable, but a trust decision needs an independently trusted root pin.
No. The report distinguishes observed functionality, compatibility findings, authenticity evidence and confidentiality checks. It cannot certify every behavior, dependency, input file or external service. Test your application’s actual user workflows.
Local processing does not mean that every possible network action is disabled. The standard engine can fetch dependencies; URL import and external inlining fetch source resources; a preview allowed to use the network runs the source’s own requests; the external signing workflow contacts its configured service. The guide itself makes no network requests. Treat source drafts, historical artifacts, workspace ZIPs, downloaded payloads and reports according to their actual contents.
Keep originals and passwords separately backed up. Prefer a stable release origin for storage and permissions. Review imported configurations and plugins before executing them. When raising a support issue, use the effective configuration, engine identity and bounded error report, removing private source and credentials first.
Implementation reference · docs/V10.4.2-RUNTIME-PRESERVATION.md · src/app-core.js · src/runtime-loader.js
A compact reference for readers moving from the first build to advanced delivery workflows.
| Term | Meaning in MLDarkMatter |
|---|---|
| AST | Abstract Syntax Tree: a structured representation of JavaScript used for syntax-aware inspection and supported edits. |
| Backpressure | A producer waits for a consumer to finish. Here, the Worker waits for acknowledgement after the main thread writes a chunk. |
| Build / artifact | A processing run and the files it produces. A successful build does not automatically imply successful execution of every feature. |
| Build ID / watermark | Traceability text attached to a build; not a cryptographic signature. |
| CORS | The browser-enforced cross-origin rules affecting requests to another origin. |
| CSP | Content Security Policy: browser-enforced rules for scripts and other resources. |
| CSSOM | The browser’s structured CSS representation used to inspect and update supported stylesheet rules. |
| Ed25519 | The digital-signature algorithm used by the external manifest and trust tooling. |
| Effective configuration | The settings actually used after validation and runtime-preservation adaptations. |
| Fingerprint | Depending on the context, a visitor-derived identifier or a hash-derived key/file identity. The optional visitor fingerprint is not proof of a person’s identity. |
| GCM | The authenticated AES mode used for encrypted payloads. |
| HSM | Hardware Security Module: external hardware that can hold and use private keys. The supplied command adapter still needs a provisioned device or service. |
| Integrity | Evidence that bytes match an expected hash or signature-bound artifact. A replaceable unsigned hash alone does not establish publisher identity. |
| Manifest | A structured delivery record, including files, sizes and hashes, suitable for external signing. |
| Nonce | A per-build value used to authorize specific scripts under the generated CSP; not a password. |
| Obfuscation | Code transformations intended to make JavaScript less understandable while preserving behavior. |
| PBKDF2 | The password-based key derivation function used before AES-GCM operations. |
| Pinning | Requiring an independently trusted root fingerprint instead of trusting whichever root arrives with a package. |
| Sandbox | A restricted execution context. A preview sandbox and a plugin Worker have different boundaries and limitations. |
| Seed | A repeatable input to transformation randomization; cryptographic salt and IV generation remain separate. |
| SHA-256 | The cryptographic hash used to identify source, artifacts and trust/publication records. |
| Smoke test | A bounded startup execution observation. It is not a complete test of all application interactions. |
| Trust-store | A signed, versioned registry of public signing keys and their acceptance/revocation policy. |
| Unicode-safe offsets | Positions measured against the original text, without length-changing case conversion before slicing. |
| Worker | A separate JavaScript execution context used to keep heavy processing away from the main UI event loop. |
Product authorship, shipped dependency notices and the optional engineering toolchain are separate layers of attribution.
| Component | Credits and role | License / version scope | Project reference |
|---|---|---|---|
| PrismJS 1.30.0 | Lea Verou and contributors. Syntax highlighting for the embedded editors. | MIT. Notice embedded below. | PrismJS ↗ |
| JSZip 3.10.1 | Stuart Knightley, David Duponchel, Franz Buchinger, António Afonso and contributors. ZIP import/export and workspace packaging. | MIT or GPL-3.0-or-later, as declared in the bundled notice. | JSZip ↗ |
| Acorn 8.15.0 | Acorn contributors. JavaScript parsing and syntax-aware tooling. | MIT. Notice embedded below. | Acorn ↗ |
| javascript-obfuscator 4.1.1 | Timofey Kachalov, Dmitry Zamotkin and contributors. Optional full transformation engine. | BSD-2-Clause in the official 4.1.1 package metadata and LICENSE.BSD. | Pinned engine license ↗ |
| html-minifier 4.0.0 | Juriy “kangax” Zaytsev; maintained by Alex Lam, with contributions from Gilmore Davidson, Hugo Wetterberg, Zoltan Frombach and others. Optional HTML minification. | MIT in the official v4.0.0 package metadata. | Pinned minifier metadata ↗ |
| Pako, through JSZip | Vitaly Puzrin, Andrei Tuputcyn and contributors. Compression code included through the distributed ZIP library. The package does not specify a separate Pako version here. | MIT in the upstream project notice. | Pako license ↗ |
| TypeScript | Microsoft and contributors. Optional development-time type checking and compilation of the canonical pipeline modules. | Apache-2.0; package declares ^5.8.0. | TypeScript license ↗ |
| esbuild | Evan Wallace and contributors. Optional development bundler and watch workflow. | MIT; package declares ^0.25.0. | esbuild license ↗ |
| Playwright | Microsoft and contributors. Browser automation in the companion checking infrastructure. | Apache-2.0. Browser engines have their own projects and notices. | Playwright license ↗ |
MIT LICENSE Copyright (c) 2012 Lea Verou Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
JSZip is dual licensed. At your choice you may use it under the MIT license *or* the GPLv3
license.
The MIT License
===============
Copyright (c) 2009-2016 Stuart Knightley, David Duponchel, Franz Buchinger, António Afonso
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in
all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
THE SOFTWARE.
GPL version 3
=============
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
Preamble
The GNU General Public License is a free, copyleft license for
software and other kinds of works.
The licenses for most software and other practical works are designed
to take away your freedom to share and change the works. By contrast,
the GNU General Public License is intended to guarantee your freedom to
share and change all versions of a program--to make sure it remains free
software for all its users. We, the Free Software Foundation, use the
GNU General Public License for most of our software; it applies also to
any other work released this way by its authors. You can apply it to
your programs, too.
When we speak of free software, we are referring to freedom, not
price. Our General Public Licenses are designed to make sure that you
have the freedom to distribute copies of free software (and charge for
them if you wish), that you receive source code or can get it if you
want it, that you can change the software or use pieces of it in new
free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you
these rights or asking you to surrender the rights. Therefore, you have
certain responsibilities if you distribute copies of the software, or if
you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether
gratis or for a fee, you must pass on to the recipients the same
freedoms that you received. You must make sure that they, too, receive
or can get the source code. And you must show them these terms so they
know their rights.
Developers that use the GNU GPL protect your rights with two steps:
(1) assert copyright on the software, and (2) offer you this License
giving you legal permission to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains
that there is no warranty for this free software. For both users' and
authors' sake, the GPL requires that modified versions be marked as
changed, so that their problems will not be attributed erroneously to
authors of previous versions.
Some devices are designed to deny users access to install or run
modified versions of the software inside them, although the manufacturer
can do so. This is fundamentally incompatible with the aim of
protecting users' freedom to change the software. The systematic
pattern of such abuse occurs in the area of products for individuals to
use, which is precisely where it is most unacceptable. Therefore, we
have designed this version of the GPL to prohibit the practice for those
products. If such problems arise substantially in other domains, we
stand ready to extend this provision to those domains in future versions
of the GPL, as needed to protect the freedom of users.
Finally, every program is threatened constantly by software patents.
States should not allow patents to restrict development and use of
software on general-purpose computers, but in those that do, we wish to
avoid the special danger that patents applied to a free program could
make it effectively proprietary. To prevent this, the GPL assures that
patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and
modification follow.
TERMS AND CONDITIONS
0. Definitions.
"This License" refers to version 3 of the GNU General Public License.
"Copyright" also means copyright-like laws that apply to other kinds of
works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this
License. Each licensee is addressed as "you". "Licensees" and
"recipients" may be individuals or organizations.
To "modify" a work means to copy from or adapt all or part of the work
in a fashion requiring copyright permission, other than the making of an
exact copy. The resulting work is called a "modified version" of the
earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based
on the Program.
To "propagate" a work means to do anything with it that, without
permission, would make you directly or secondarily liable for
infringement under applicable copyright law, except executing it on a
computer or modifying a private copy. Propagation includes copying,
distribution (with or without modification), making available to the
public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other
parties to make or receive copies. Mere interaction with a user through
a computer network, with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices"
to the extent that it includes a convenient and prominently visible
feature that (1) displays an appropriate copyright notice, and (2)
tells the user that there is no warranty for the work (except to the
extent that warranties are provided), that licensees may convey the
work under this License, and how to view a copy of this License. If
the interface presents a list of user commands or options, such as a
menu, a prominent item in the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work
for making modifications to it. "Object code" means any non-source
form of a work.
A "Standard Interface" means an interface that either is an official
standard defined by a recognized standards body, or, in the case of
interfaces specified for a particular programming language, one that
is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other
than the work as a whole, that (a) is included in the normal form of
packaging a Major Component, but which is not part of that Major
Component, and (b) serves only to enable use of the work with that
Major Component, or to implement a Standard Interface for which an
implementation is available to the public in source code form. A
"Major Component", in this context, means a major essential component
(kernel, window system, and so on) of the specific operating system
(if any) on which the executable work runs, or a compiler used to
produce the work, or an object code interpreter used to run it.
The "Corresponding Source" for a work in object code form means all
the source code needed to generate, install, and (for an executable
work) run the object code and to modify the work, including scripts to
control those activities. However, it does not include the work's
System Libraries, or general-purpose tools or generally available free
programs which are used unmodified in performing those activities but
which are not part of the work. For example, Corresponding Source
includes interface definition files associated with source files for
the work, and the source code for shared libraries and dynamically
linked subprograms that the work is specifically designed to require,
such as by intimate data communication or control flow between those
subprograms and other parts of the work.
The Corresponding Source need not include anything that users
can regenerate automatically from other parts of the Corresponding
Source.
The Corresponding Source for a work in source code form is that
same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of
copyright on the Program, and are irrevocable provided the stated
conditions are met. This License explicitly affirms your unlimited
permission to run the unmodified Program. The output from running a
covered work is covered by this License only if the output, given its
content, constitutes a covered work. This License acknowledges your
rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not
convey, without conditions so long as your license otherwise remains
in force. You may convey covered works to others for the sole purpose
of having them make modifications exclusively for you, or provide you
with facilities for running those works, provided that you comply with
the terms of this License in conveying all material for which you do
not control copyright. Those thus making or running the covered works
for you must do so exclusively on your behalf, under your direction
and control, on terms that prohibit them from making any copies of
your copyrighted material outside their relationship with you.
Conveying under any other circumstances is permitted solely under
the conditions stated below. Sublicensing is not allowed; section 10
makes it unnecessary.
3. Protecting Users' Legal Rights From Anti-Circumvention Law.
No covered work shall be deemed part of an effective technological
measure under any applicable law fulfilling obligations under article
11 of the WIPO copyright treaty adopted on 20 December 1996, or
similar laws prohibiting or restricting circumvention of such
measures.
When you convey a covered work, you waive any legal power to forbid
circumvention of technological measures to the extent such circumvention
is effected by exercising rights under this License with respect to
the covered work, and you disclaim any intention to limit operation or
modification of the work as a means of enforcing, against the work's
users, your or third parties' legal rights to forbid circumvention of
technological measures.
4. Conveying Verbatim Copies.
You may convey verbatim copies of the Program's source code as you
receive it, in any medium, provided that you conspicuously and
appropriately publish on each copy an appropriate copyright notice;
keep intact all notices stating that this License and any
non-permissive terms added in accord with section 7 apply to the code;
keep intact all notices of the absence of any warranty; and give all
recipients a copy of this License along with the Program.
You may charge any price or no price for each copy that you convey,
and you may offer support or warranty protection for a fee.
5. Conveying Modified Source Versions.
You may convey a work based on the Program, or the modifications to
produce it from the Program, in the form of source code under the
terms of section 4, provided that you also meet all of these conditions:
a) The work must carry prominent notices stating that you modified
it, and giving a relevant date.
b) The work must carry prominent notices stating that it is
released under this License and any conditions added under section
7. This requirement modifies the requirement in section 4 to
"keep intact all notices".
c) You must license the entire work, as a whole, under this
License to anyone who comes into possession of a copy. This
License will therefore apply, along with any applicable section 7
additional terms, to the whole of the work, and all its parts,
regardless of how they are packaged. This License gives no
permission to license the work in any other way, but it does not
invalidate such permission if you have separately received it.
d) If the work has interactive user interfaces, each must display
Appropriate Legal Notices; however, if the Program has interactive
interfaces that do not display Appropriate Legal Notices, your
work need not make them do so.
A compilation of a covered work with other separate and independent
works, which are not by their nature extensions of the covered work,
and which are not combined with it such as to form a larger program,
in or on a volume of a storage or distribution medium, is called an
"aggregate" if the compilation and its resulting copyright are not
used to limit the access or legal rights of the compilation's users
beyond what the individual works permit. Inclusion of a covered work
in an aggregate does not cause this License to apply to the other
parts of the aggregate.
6. Conveying Non-Source Forms.
You may convey a covered work in object code form under the terms
of sections 4 and 5, provided that you also convey the
machine-readable Corresponding Source under the terms of this License,
in one of these ways:
a) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by the
Corresponding Source fixed on a durable physical medium
customarily used for software interchange.
b) Convey the object code in, or embodied in, a physical product
(including a physical distribution medium), accompanied by a
written offer, valid for at least three years and valid for as
long as you offer spare parts or customer support for that product
model, to give anyone who possesses the object code either (1) a
copy of the Corresponding Source for all the software in the
product that is covered by this License, on a durable physical
medium customarily used for software interchange, for a price no
more than your reasonable cost of physically performing this
conveying of source, or (2) access to copy the
Corresponding Source from a network server at no charge.
c) Convey individual copies of the object code with a copy of the
written offer to provide the Corresponding Source. This
alternative is allowed only occasionally and noncommercially, and
only if you received the object code with such an offer, in accord
with subsection 6b.
d) Convey the object code by offering access from a designated
place (gratis or for a charge), and offer equivalent access to the
Corresponding Source in the same way through the same place at no
further charge. You need not require recipients to copy the
Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source
may be on a different server (operated by you or a third party)
that supports equivalent copying facilities, provided you maintain
clear directions next to the object code saying where to find the
Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is
available for as long as needed to satisfy these requirements.
e) Convey the object code using peer-to-peer transmission, provided
you inform other peers where the object code and Corresponding
Source of the work are being offered to the general public at no
charge under subsection 6d.
A separable portion of the object code, whose source code is excluded
from the Corresponding Source as a System Library, need not be
included in conveying the object code work.
A "User Product" is either (1) a "consumer product", which means any
tangible personal property which is normally used for personal, family,
or household purposes, or (2) anything designed or sold for incorporation
into a dwelling. In determining whether a product is a consumer product,
doubtful cases shall be resolved in favor of coverage. For a particular
product received by a particular user, "normally used" refers to a
typical or common use of that class of product, regardless of the status
of the particular user or of the way in which the particular user
actually uses, or expects or is expected to use, the product. A product
is a consumer product regardless of whether the product has substantial
commercial, industrial or non-consumer uses, unless such uses represent
the only significant mode of use of the product.
"Installation Information" for a User Product means any methods,
procedures, authorization keys, or other information required to install
and execute modified versions of a covered work in that User Product from
a modified version of its Corresponding Source. The information must
suffice to ensure that the continued functioning of the modified object
code is in no case prevented or interfered with solely because
modification has been made.
If you convey an object code work under this section in, or with, or
specifically for use in, a User Product, and the conveying occurs as
part of a transaction in which the right of possession and use of the
User Product is transferred to the recipient in perpetuity or for a
fixed term (regardless of how the transaction is characterized), the
Corresponding Source conveyed under this section must be accompanied
by the Installation Information. But this requirement does not apply
if neither you nor any third party retains the ability to install
modified object code on the User Product (for example, the work has
been installed in ROM).
The requirement to provide Installation Information does not include a
requirement to continue to provide support service, warranty, or updates
for a work that has been modified or installed by the recipient, or for
the User Product in which it has been modified or installed. Access to a
network may be denied when the modification itself materially and
adversely affects the operation of the network or violates the rules and
protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided,
in accord with this section must be in a format that is publicly
documented (and with an implementation available to the public in
source code form), and must require no special password or key for
unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this
License by making exceptions from one or more of its conditions.
Additional permissions that are applicable to the entire Program shall
be treated as though they were included in this License, to the extent
that they are valid under applicable law. If additional permissions
apply only to part of the Program, that part may be used separately
under those permissions, but the entire Program remains governed by
this License without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option
remove any additional permissions from that copy, or from any part of
it. (Additional permissions may be written to require their own
removal in certain cases when you modify the work.) You may place
additional permissions on material, added by you to a covered work,
for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you
add to a covered work, you may (if authorized by the copyright holders of
that material) supplement the terms of this License with terms:
a) Disclaiming warranty or limiting liability differently from the
terms of sections 15 and 16 of this License; or
b) Requiring preservation of specified reasonable legal notices or
author attributions in that material or in the Appropriate Legal
Notices displayed by works containing it; or
c) Prohibiting misrepresentation of the origin of that material, or
requiring that modified versions of such material be marked in
reasonable ways as different from the original version; or
d) Limiting the use for publicity purposes of names of licensors or
authors of the material; or
e) Declining to grant rights under trademark law for use of some
trade names, trademarks, or service marks; or
f) Requiring indemnification of licensors and authors of that
material by anyone who conveys the material (or modified versions of
it) with contractual assumptions of liability to the recipient, for
any liability that these contractual assumptions directly impose on
those licensors and authors.
All other non-permissive additional terms are considered "further
restrictions" within the meaning of section 10. If the Program as you
received it, or any part of it, contains a notice stating that it is
governed by this License along with a term that is a further
restriction, you may remove that term. If a license document contains
a further restriction but permits relicensing or conveying under this
License, you may add to a covered work material governed by the terms
of that license document, provided that the further restriction does
not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you
must place, in the relevant source files, a statement of the
additional terms that apply to those files, or a notice indicating
where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the
form of a separately written license, or stated as exceptions;
the above requirements apply either way.
8. Termination.
You may not propagate or modify a covered work except as expressly
provided under this License. Any attempt otherwise to propagate or
modify it is void, and will automatically terminate your rights under
this License (including any patent licenses granted under the third
paragraph of section 11).
However, if you cease all violation of this License, then your
license from a particular copyright holder is reinstated (a)
provisionally, unless and until the copyright holder explicitly and
finally terminates your license, and (b) permanently, if the copyright
holder fails to notify you of the violation by some reasonable means
prior to 60 days after the cessation.
Moreover, your license from a particular copyright holder is
reinstated permanently if the copyright holder notifies you of the
violation by some reasonable means, this is the first time you have
received notice of violation of this License (for any work) from that
copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the
licenses of parties who have received copies or rights from you under
this License. If your rights have been terminated and not permanently
reinstated, you do not qualify to receive new licenses for the same
material under section 10.
9. Acceptance Not Required for Having Copies.
You are not required to accept this License in order to receive or
run a copy of the Program. Ancillary propagation of a covered work
occurring solely as a consequence of using peer-to-peer transmission
to receive a copy likewise does not require acceptance. However,
nothing other than this License grants you permission to propagate or
modify any covered work. These actions infringe copyright if you do
not accept this License. Therefore, by modifying or propagating a
covered work, you indicate your acceptance of this License to do so.
10. Automatic Licensing of Downstream Recipients.
Each time you convey a covered work, the recipient automatically
receives a license from the original licensors, to run, modify and
propagate that work, subject to this License. You are not responsible
for enforcing compliance by third parties with this License.
An "entity transaction" is a transaction transferring control of an
organization, or substantially all assets of one, or subdividing an
organization, or merging organizations. If propagation of a covered
work results from an entity transaction, each party to that
transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could
give under the previous paragraph, plus a right to possession of the
Corresponding Source of the work from the predecessor in interest, if
the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the
rights granted or affirmed under this License. For example, you may
not impose a license fee, royalty, or other charge for exercise of
rights granted under this License, and you may not initiate litigation
(including a cross-claim or counterclaim in a lawsuit) alleging that
any patent claim is infringed by making, using, selling, offering for
sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this
License of the Program or a work on which the Program is based. The
work thus licensed is called the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims
owned or controlled by the contributor, whether already acquired or
hereafter acquired, that would be infringed by some manner, permitted
by this License, of making, using, or selling its contributor version,
but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For
purposes of this definition, "control" includes the right to grant
patent sublicenses in a manner consistent with the requirements of
this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free
patent license under the contributor's essential patent claims, to
make, use, sell, offer for sale, import and otherwise run, modify and
propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express
agreement or commitment, however denominated, not to enforce a patent
(such as an express permission to practice a patent or covenant not to
sue for patent infringement). To "grant" such a patent license to a
party means to make such an agreement or commitment not to enforce a
patent against the party.
If you convey a covered work, knowingly relying on a patent license,
and the Corresponding Source of the work is not available for anyone
to copy, free of charge and under the terms of this License, through a
publicly available network server or other readily accessible means,
then you must either (1) cause the Corresponding Source to be so
available, or (2) arrange to deprive yourself of the benefit of the
patent license for this particular work, or (3) arrange, in a manner
consistent with the requirements of this License, to extend the patent
license to downstream recipients. "Knowingly relying" means you have
actual knowledge that, but for the patent license, your conveying the
covered work in a country, or your recipient's use of the covered work
in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or
arrangement, you convey, or propagate by procuring conveyance of, a
covered work, and grant a patent license to some of the parties
receiving the covered work authorizing them to use, propagate, modify
or convey a specific copy of the covered work, then the patent license
you grant is automatically extended to all recipients of the covered
work and works based on it.
A patent license is "discriminatory" if it does not include within
the scope of its coverage, prohibits the exercise of, or is
conditioned on the non-exercise of one or more of the rights that are
specifically granted under this License. You may not convey a covered
work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment
to the third party based on the extent of your activity of conveying
the work, and under which the third party grants, to any of the
parties who would receive the covered work from you, a discriminatory
patent license (a) in connection with copies of the covered work
conveyed by you (or copies made from those copies), or (b) primarily
for and in connection with specific products or compilations that
contain the covered work, unless you entered into that arrangement,
or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting
any implied license or other defenses to infringement that may
otherwise be available to you under applicable patent law.
12. No Surrender of Others' Freedom.
If conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License. If you cannot convey a
covered work so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you may
not convey it at all. For example, if you agree to terms that obligate you
to collect a royalty for further conveying from those to whom you convey
the Program, the only way you could satisfy both those terms and this
License would be to refrain entirely from conveying the Program.
13. Use with the GNU Affero General Public License.
Notwithstanding any other provision of this License, you have
permission to link or combine any covered work with a work licensed
under version 3 of the GNU Affero General Public License into a single
combined work, and to convey the resulting work. The terms of this
License will continue to apply to the part which is the covered work,
but the special requirements of the GNU Affero General Public License,
section 13, concerning interaction through a network will apply to the
combination as such.
14. Revised Versions of this License.
The Free Software Foundation may publish revised and/or new versions of
the GNU General Public License from time to time. Such new versions will
be similar in spirit to the present version, but may differ in detail to
address new problems or concerns.
Each version is given a distinguishing version number. If the
Program specifies that a certain numbered version of the GNU General
Public License "or any later version" applies to it, you have the
option of following the terms and conditions either of that numbered
version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the
GNU General Public License, you may choose any version ever published
by the Free Software Foundation.
If the Program specifies that a proxy can decide which future
versions of the GNU General Public License can be used, that proxy's
public statement of acceptance of a version permanently authorizes you
to choose that version for the Program.
Later license versions may give you additional or different
permissions. However, no additional obligations are imposed on any
author or copyright holder as a result of your choosing to follow a
later version.
15. Disclaimer of Warranty.
THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY
APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT
HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY
OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM
IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF
ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
16. Limitation of Liability.
IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING
WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS
THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY
GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE
USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF
DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD
PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS),
EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF
SUCH DAMAGES.
17. Interpretation of Sections 15 and 16.
If the disclaimer of warranty and limitation of liability provided
above cannot be given local legal effect according to their terms,
reviewing courts shall apply local law that most closely approximates
an absolute waiver of all civil liability in connection with the
Program, unless a warranty or assumption of liability accompanies a
copy of the Program in return for a fee.
END OF TERMS AND CONDITIONS
MIT License Copyright (C) 2012-2022 by various contributors (see AUTHORS) Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Node.js, Python, Chromium, Firefox and WebKit belong to their respective projects and contributors. They support development, automation or execution environments; they are not all embedded inside the browser application. PowerShell-style visuals describe an interface aesthetic and do not imply a Microsoft product, affiliation or endorsement.
Implementation reference · src/help-content.js: CREDITS_HELP · vendor/manifest.json · vendor/LICENSES.md · package.json
The contents describe the delivered MLDarkMatter v10.4.2 implementation and its companion package.
| Area | Primary package references |
|---|---|
| Product and release behavior | README.md; docs/V10.4.2-RUNTIME-PRESERVATION.md; the v10.4.2 runtime notes and validation records. |
| Interface and orchestration | src/index.html, src/app-core.js, src/styles.css, src/icons.js, src/help-content.js. |
| Appearance and localization | src/themes.js, src/i18n.js, src/i18n-expert.js. |
| Startup and public controls | src/launch-options.js; public API and internal console handlers in src/app-core.js. |
| Transforms and runtime | src/css-ast.js, src/runtime-loader.js, src/ts/, src/types/contracts.ts. |
| Signing and publication | tools/; docs/HSM-REMOTE-SIGNING.md, docs/TRUST-PUBLICATION.md; signed-manifest and trust documentation. |
| Build and dependencies | build/build_dist.py, build/esbuild.mjs, package.json, vendor/manifest.json and the three bundled vendor license files. |
Implementation references throughout this guide are paths inside the companion source package, not external services that must be reached to read the guide. License links identify upstream notices where an attribution check was needed. No feature has been inferred solely from an older changelog entry.
This guide’s screen collection is not a claim that the complete source package’s browser matrix, production signer or physical HSM was exercised during documentation. The release’s own recorded validation and known limitations are described separately above.
3daad8fc22c9f06c32884ec2d30b66b68ea176b6f0508d1da33da076e9f9be59Keep this guide and the standard application together. The main launch link stays relative, so the pair can be distributed in the same folder.
Launch MLDarkMatter ↗