[]
        
(Showing Draft Content)

Software Bill of Materials

DsDataViewer provides a Software Bill of Materials (SBOM) to help customers review the software components included in the product. An SBOM improves software supply chain transparency by listing the packages and dependencies used in a specific product release.

You can use the SBOM to support internal security reviews, license compliance checks, and other software governance requirements.

SBOM Format

The SBOM for DsDataViewer is provided in CycloneDX format.

The current SBOM information includes the following product metadata:

  • Product: Document Solutions Data Viewer

  • Package: @mescius/dsdataviewer

  • Version: Aligned with the latest official release

  • SBOM format: CycloneDX 1.6

  • Supplier: MESCIUS inc.

What the SBOM Includes

The SBOM for DsDataViewer includes information about the components used in the product release, such as:

  • Product package name and version

  • Third-party dependencies

  • Transitive dependencies

  • Open-source components

  • License information, when available

  • Package identifiers and versions

  • Supplier metadata

  • Known vulnerability references, when available

This information can help you identify the components included in a release and review their licensing and security status.

Component Categories

The SBOM for DsDataViewer can include components from the following categories:

  • Document Solutions Data Viewer product packages

  • Third-party open-source libraries

  • Transitive npm dependencies

  • Supporting packages used for data parsing and processing

For example, the SBOM may include packages used for data file parsing and preview features, such as libraries for Arrow, Parquet, and CSV processing.

Obtain an SBOM

The SBOM for DsDataViewer is available upon request.

To obtain the SBOM for a specific release, please contact MESCIUS Support.

Notes:

  • The SBOM is generated for a specific product release.

  • The complete dependency list is provided in the SBOM file.

  • Vulnerability information may change over time and should be validated against current security databases when needed.