← Home

@blocknote/server-util

npm Repository Homepage
51
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

yousefedmatthewlipskinperez0111

Keywords

reactjavascripteditortypescriptprosemirrorwysiwygrich-text-editornotionyjsblock-basedtiptap

Versions (showing 51 of 65)

View all versions
Version Deps Published
0.52.0 5 / 11
0.51.4 8 / 11
0.51.3 8 / 11
0.51.2 8 / 11
0.51.1 8 / 11
0.51.0 8 / 11
0.50.0 8 / 11
0.49.0 8 / 11
0.48.1 8 / 11
0.48.0 8 / 11
0.47.3 8 / 11
0.47.2 8 / 11
0.47.1 8 / 11
0.47.0 8 / 11
0.46.2 8 / 11
0.46.1 8 / 11
0.46.0 8 / 11
0.45.0 8 / 11
0.44.2 8 / 11
0.44.1 8 / 11
0.44.0 8 / 11
0.43.0 8 / 11
0.42.3 8 / 11
0.42.2 8 / 11
0.42.1 8 / 11
0.42.0 8 / 11
0.41.1 8 / 11
0.41.0 8 / 11
0.40.0 8 / 11
0.39.2 8 / 11
0.39.1 8 / 11
0.39.0 8 / 11
0.38.0 8 / 11
0.37.0 8 / 11
0.36.1 8 / 11
0.33.0 8 / 9
0.32.0 8 / 9
0.31.3 8 / 9
0.31.2 8 / 9
0.31.1 8 / 9
0.31.0 8 / 9
0.30.1 8 / 9
0.24.2 8 / 10
0.24.1 8 / 10
0.24.0 8 / 10
0.23.6 8 / 10
0.23.5 8 / 10
0.23.4 8 / 10
0.23.3 8 / 10
0.23.2 8 / 10
0.23.1 8 / 10

v0.52.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.

v0.51.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.

v0.24.2

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: yousefed → matthewlipski (on 2025-02-28, known maintainer) provenance

This version was published by a different npm account (matthewlipski) than the most recent previously approved version (yousefed) on 2025-02-28, but matthewlipski is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.24.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: yousefed → matthewlipski (on 2025-02-20, known maintainer) provenance

This version was published by a different npm account (matthewlipski) than the most recent previously approved version (yousefed) on 2025-02-20, but matthewlipski is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.24.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.23.6

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: nperez0111 → yousefed (on 2025-02-12, known maintainer) provenance

This version was published by a different npm account (yousefed) than the most recent previously approved version (nperez0111) on 2025-02-12, but yousefed is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v0.23.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.23.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.23.3

2 findings
MEDIUM Publisher changed: matthewlipski → nperez0111 (on 2025-02-10, unremoved on npm for 523d) provenance

This version was published by a different npm account (nperez0111) than the most recent previously approved version (matthewlipski) on 2025-02-10. It has since remained available on npm for 523 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.23.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.23.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: yousefed → matthewlipski (on 2025-01-27, known maintainer) provenance

This version was published by a different npm account (matthewlipski) than the most recent previously approved version (yousefed) on 2025-01-27, but matthewlipski is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.