@tiptap/extension-placeholder
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): tiptap-bot is the org's CI publisher with 205 approved packages; transition from _bdbch is a documented org-level change. | ai | |
| provenance | missing-githead | AI (provenance): SLSA provenance attestation present; gitHead absence is a side-effect of the CI/CD migration, not a supply chain gap. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): arnaugomeztiptap follows tiptap org naming; consistent with org-level maintainer expansion. | ai |
Versions (showing 51 of 89)
| Version | Deps | Published |
|---|---|---|
| 3.26.0 | 0 / 1 | |
| 3.25.0 | 0 / 1 | |
| 3.24.0 | 0 / 1 | |
| 3.23.6 | 0 / 1 | |
| 3.23.5 | 0 / 1 | |
| 3.23.4 | 0 / 1 | |
| 3.23.2 | 0 / 1 | |
| 3.23.1 | 0 / 1 | |
| 3.22.5 | 0 / 1 | |
| 3.22.4 | 0 / 1 | |
| 3.22.3 | 0 / 1 | |
| 3.22.2 | 0 / 1 | |
| 3.22.1 | 0 / 1 | |
| 3.22.0 | 0 / 1 | |
| 3.21.0 | 0 / 1 | |
| 3.20.6 | 0 / 1 | |
| 3.20.5 | 0 / 1 | |
| 3.20.4 | 0 / 1 | |
| 3.20.3 | 0 / 1 | |
| 3.20.2 | 0 / 1 | |
| 3.20.1 | 0 / 1 | |
| 3.20.0 | 0 / 1 | |
| 3.19.0 | 0 / 1 | |
| 3.18.0 | 0 / 1 | |
| 3.17.1 | 0 / 1 | |
| 3.17.0 | 0 / 1 | |
| 3.16.0 | 0 / 1 | |
| 3.15.3 | 0 / 1 | |
| 3.15.2 | 0 / 1 | |
| 3.15.1 | 0 / 1 | |
| 3.15.0 | 0 / 1 | |
| 3.14.0 | 0 / 1 | |
| 3.13.0 | 0 / 1 | |
| 3.12.1 | 0 / 1 | |
| 3.12.0 | 0 / 1 | |
| 3.11.1 | 0 / 1 | |
| 3.11.0 | 0 / 1 | |
| 3.10.8 | 0 / 1 | |
| 3.10.7 | 0 / 1 | |
| 3.10.6 | 0 / 1 | |
| 3.10.5 | 0 / 1 | |
| 3.10.4 | 0 / 1 | |
| 3.10.3 | 0 / 1 | |
| 3.10.2 | 0 / 1 | |
| 3.10.1 | 0 / 1 | |
| 3.10.0 | 0 / 1 | |
| 3.9.1 | 0 / 1 | |
| 3.9.0 | 0 / 1 | |
| 3.8.0 | 0 / 1 | |
| 3.7.2 | 0 / 1 | |
| 3.7.1 | 0 / 1 |
v3.26.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.25.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.24.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.23.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.23.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.23.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.23.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.23.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.22.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.21.0
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.20.6
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-03-27. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.17.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
This version was published by a different npm account than previous versions on 2026-01-24. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.8.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.7.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.