← Home

dockview-core

npm Repository Homepage
25
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

mathuo

Keywords

splitviewsplit-viewgridviewgrid-viewdockviewdock-viewgridtabslayoutlayout managerdock layoutdockdockingsplitterdrag-and-dropdragdroptouchmobiletypescriptzero-dependencyide-layoutpanelresizablefloatingserializationworkbenchvanilla

Versions (showing 25 of 25)

Version Deps Published
7.0.4 0 / 0
7.0.3 0 / 0
7.0.2 0 / 0
6.6.1 0 / 0
6.6.0 0 / 0
6.5.0 0 / 0
6.4.0 0 / 0
6.3.0 0 / 0
6.2.2 0 / 0
6.2.1 0 / 0
6.1.1 0 / 0
6.0.7 0 / 0
6.0.6 0 / 0
6.0.5 0 / 0
6.0.3 0 / 0
6.0.1 0 / 0
6.0.0 0 / 0
5.2.0 0 / 0
5.1.0 0 / 0
5.0.0 0 / 0
4.13.1 0 / 0
4.13.0 0 / 0
4.12.0 0 / 0
4.11.0 0 / 0
4.10.0 0 / 0

v7.0.4

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v7.0.3

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v5.1.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v5.0.0

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: mathuo → GitHub Actions (on 2026-02-16, now via trusted publisher with provenance) provenance

This version was published by a different npm account (GitHub Actions) than the most recent previously approved version (mathuo) on 2026-02-16, but it carries Sigstore provenance attestation. This means the package moved to a trusted publisher (CI/CD with OIDC, e.g. GitHub Actions) — a supply-chain integrity improvement, not a compromise, since a stolen npm token cannot forge provenance bound to the source repository. Recorded as INFO for audit trail.

v4.13.1

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.13.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.12.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.11.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v4.10.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.