← Home

@hocuspocus/common

npm Repository Homepage

shared code for multiple Hocuspocus packages

5
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

patrickbabertimoisikjanthurausvenadlung_bdbchtiptap-bot

Keywords

hocuspocus

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from bot account to GitHub Actions CI with SLSA provenance; legitimate CI migration for this org. ai
dependencies unvetted-dep:lib0 AI (dependencies): lib0 is the well-known utility library by Y.js author Kevin Jahns, a standard dependency in the collaborative editing ecosystem. Its use in Hocuspocus is expected and stable across versions. ai

Versions (showing 5 of 5)

Version Deps Published
4.1.0 1 / 0
4.0.0 1 / 0
3.4.4 1 / 0
3.4.3 1 / 0
3.4.1 1 / 0

v4.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.

v4.0.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.

v3.4.4

2 findings
HIGH Publisher changed: tiptap-bot → GitHub Actions (on 2026-01-25) provenance

This version was published by a different npm account than previous versions on 2026-01-25. This could indicate a legitimate maintainer transition or an account compromise.

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.

v3.4.3

2 findings
HIGH Publisher changed: tiptap-bot → GitHub Actions (on 2025-12-15) provenance

This version was published by a different npm account than previous versions on 2025-12-15. This could indicate a legitimate maintainer transition or an account compromise.

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.

v3.4.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.