← Home

@tiptap/extension-collaboration-cursor

npm Repository Homepage
51
Versions
—
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

nperez0111timoisikpatrickbabersvenadlung_bdbch

Keywords

tiptaptiptap extension

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Legitimate ueberdosis maintainer handoff; publisher has strong clean track record. ai
maintainer-change maintainer-added AI (maintainer-change): Same handoff; nperez0111 is established tiptap maintainer. ai

Versions (showing 51 of 71)

View all versions
Version Deps Published
2.27.2 0 / 2
2.26.3 0 / 2
2.26.2 0 / 2
2.26.1 0 / 2
2.26.0 0 / 2
2.25.1 0 / 2
2.25.0 0 / 2
2.24.2 0 / 2
2.24.1 0 / 2
2.24.0 0 / 2
2.23.1 0 / 2
2.23.0 0 / 2
2.22.3 0 / 2
2.22.2 0 / 2
2.22.1 0 / 2
2.22.0 0 / 2
2.14.1 0 / 2
2.14.0 0 / 2
2.13.0 0 / 2
2.12.0 0 / 2
2.11.9 0 / 2
2.11.7 0 / 2
2.11.6 0 / 2
2.11.5 0 / 2
2.11.4 0 / 2
2.11.3 0 / 2
2.11.2 0 / 2
2.11.1 0 / 2
2.11.0 0 / 2
2.10.4 0 / 2
2.10.3 0 / 2
2.10.2 0 / 2
2.10.1 0 / 2
2.10.0 0 / 2
2.9.1 0 / 2
2.9.0 0 / 2
2.8.0 0 / 2
2.5.2 0 / 2
2.5.0 0 / 2
2.4.0 0 / 2
2.3.2 0 / 2
2.3.1 0 / 2
2.3.0 0 / 2
2.2.6 0 / 2
2.2.5 0 / 2
2.2.4 0 / 2
2.2.3 0 / 2
2.2.2 0 / 2
2.2.1 0 / 2
2.2.0 0 / 2
2.1.16 0 / 2

v2.11.7

2 findings
HIGH Publisher changed: _bdbch → tiptap-bot (on 2025-03-30) provenance

This version was published by a different npm account than previous versions on 2025-03-30. 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.

v2.11.6

2 findings
HIGH Publisher changed: _bdbch → tiptap-bot (on 2025-03-28) provenance

This version was published by a different npm account than previous versions on 2025-03-28. 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.

v2.11.5

2 findings
HIGH Publisher changed: _bdbch → tiptap-bot (on 2025-01-31) provenance

This version was published by a different npm account than previous versions on 2025-01-31. 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.

v2.11.4

2 findings
HIGH Publisher changed: _bdbch → tiptap-bot (on 2025-01-30) provenance

This version was published by a different npm account than previous versions on 2025-01-30. 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.

v2.11.3

2 findings
HIGH Publisher changed: _bdbch → tiptap-bot (on 2025-01-22) provenance

This version was published by a different npm account than previous versions on 2025-01-22. 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.

v2.11.2

2 findings
HIGH Publisher changed: _bdbch → tiptap-bot (on 2025-01-10) provenance

This version was published by a different npm account than previous versions on 2025-01-10. 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.

v2.11.1

2 findings
HIGH Publisher changed: _bdbch → tiptap-bot (on 2025-01-10) provenance

This version was published by a different npm account than previous versions on 2025-01-10. 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.

v2.11.0

2 findings
HIGH Publisher changed: _bdbch → nperez0111 (on 2024-12-30) provenance

This version was published by a different npm account than previous versions on 2024-12-30. 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.

v2.10.4

2 findings
HIGH Publisher changed: _bdbch → nperez0111 (on 2024-12-19) provenance

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

LOW No provenance attestation provenance

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

v2.10.3

2 findings
HIGH Publisher changed: _bdbch → nperez0111 (on 2024-11-26) provenance

This version was published by a different npm account than previous versions on 2024-11-26. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.10.2

2 findings
HIGH Publisher changed: _bdbch → nperez0111 (on 2024-11-22) provenance

This version was published by a different npm account than previous versions on 2024-11-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.10.1

2 findings
HIGH Publisher changed: _bdbch → nperez0111 (on 2024-11-21) provenance

This version was published by a different npm account than previous versions on 2024-11-21. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.10.0

2 findings
HIGH Publisher changed: _bdbch → nperez0111 (on 2024-11-20) provenance

This version was published by a different npm account than previous versions on 2024-11-20. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.9.1

2 findings
HIGH Publisher changed: _bdbch → nperez0111 (on 2024-10-23) provenance

This version was published by a different npm account than previous versions on 2024-10-23. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.9.0

2 findings
HIGH Publisher changed: _bdbch → nperez0111 (on 2024-10-22) provenance

This version was published by a different npm account than previous versions on 2024-10-22. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.8.0

2 findings
HIGH Publisher changed: _bdbch → nperez0111 (on 2024-09-30) provenance

This version was published by a different npm account than previous versions on 2024-09-30. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.5.2

2 findings
HIGH Publisher changed: _bdbch → nperez0111 (on 2024-07-17) provenance

This version was published by a different npm account than previous versions on 2024-07-17. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.5.0

2 findings
HIGH Publisher changed: _bdbch → nperez0111 (on 2024-07-14) provenance

This version was published by a different npm account than previous versions on 2024-07-14. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.4.0

1 finding
LOW No provenance attestation provenance

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

v2.3.2

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.

v2.3.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.

v2.3.0

1 finding
LOW No provenance attestation provenance

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

v2.2.6

1 finding
LOW No provenance attestation provenance

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

v2.2.5

1 finding
LOW No provenance attestation provenance

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

v2.2.4

1 finding
LOW No provenance attestation provenance

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

v2.2.3

1 finding
LOW No provenance attestation provenance

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

v2.2.2

1 finding
LOW No provenance attestation provenance

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

v2.2.1

1 finding
LOW No provenance attestation provenance

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

v2.2.0

1 finding
LOW No provenance attestation provenance

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

v2.1.16

1 finding
LOW No provenance attestation provenance

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