Skip to content

    Development documentation — this describes the current development branch. Documented behavior may not exist in the latest release.

    Fork compatibility

    This page states how the ForgeGuard fork relates to upstream tanabe/markdown-live-preview: what it is based on, where it diverges, and how versions line up. For general platform support (Node, container, Kubernetes, browsers), see Reference: compatibility.

    The fork tracks upstream tagged releases and reapplies the ForgeGuard privacy, container, and Helm changes on top. It does not continuously merge upstream’s default branch, so upstream changes made after the tracked point are not automatically present.

    AreaUpstreamThis fork
    Mermaid diagramsRendered in current upstream.Not supported. Reconciling Mermaid with this fork’s sanitization, CSP, and external-resource policy is deferred. Do not rely on Mermaid rendering here.
    Monaco editorHistorically loaded from a runtime CDN.Bundled from local dependencies.
    AnalyticsEnabled by default upstream.Opt-in, off by default.
    Remote imagesRendered.Blocked by default; opt-in toggle.
    PersistenceEffectively indefinite.Bounded (content 30 days, settings 365 days).
    DistributionFirebase Hosting / hosted site.Self-hostable GHCR container and OCI Helm chart.

    Container images are currently built for linux/amd64 only. For other architectures, build the image from source (see Container).

    ArtifactVersionNotes
    Application1.0.0package.json version and the chart’s appVersion.
    Helm chart0.1.1Versioned independently of the image.
    Container imagelatest + sha-<commit>Rolling and immutable tags; not semver-tagged.

    The image tag and chart version are independent — pin both for reproducible deployments.

    If you are moving from an upstream build or the hosted site, expect the privacy toggles to default to the restrictive setting and Mermaid diagrams not to render. See Migration from upstream.