@plasmicpkgs/tiptap
Tiptap for React
Supply chain provenance
Status for the latest visible version.
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
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 0.0.46 | 16 / 16 | |
| 0.0.45 | 16 / 16 | |
| 0.0.44 | 16 / 16 | |
| 0.0.43 | 16 / 16 | |
| 0.0.42 | 16 / 16 | |
| 0.0.41 | 16 / 16 | |
| 0.0.40 | 16 / 16 | |
| 0.0.39 | 16 / 16 | |
| 0.0.38 | 16 / 16 | |
| 0.0.37 | 16 / 16 | |
| 0.0.36 | 16 / 16 | |
| 0.0.35 | 16 / 16 | |
| 0.0.34 | 16 / 16 | |
| 0.0.33 | 16 / 16 | |
| 0.0.32 | 16 / 16 | |
| 0.0.31 | 16 / 16 | |
| 0.0.30 | 16 / 16 | |
| 0.0.29 | 16 / 16 | |
| 0.0.28 | 16 / 16 | |
| 0.0.27 | 16 / 16 | |
| 0.0.26 | 16 / 16 | |
| 0.0.25 | 16 / 16 | |
| 0.0.24 | 16 / 16 | |
| 0.0.23 | 16 / 16 | |
| 0.0.22 | 16 / 16 | |
| 0.0.21 | 16 / 16 | |
| 0.0.20 | 16 / 16 | |
| 0.0.19 | 16 / 16 | |
| 0.0.18 | 16 / 16 | |
| 0.0.17 | 16 / 16 | |
| 0.0.16 | 16 / 16 | |
| 0.0.15 | 16 / 16 | |
| 0.0.14 | 16 / 16 | |
| 0.0.13 | 16 / 16 | |
| 0.0.12 | 16 / 16 | |
| 0.0.11 | 16 / 16 | |
| 0.0.10 | 16 / 16 | |
| 0.0.9 | 16 / 16 | |
| 0.0.8 | 16 / 16 | |
| 0.0.7 | 16 / 16 | |
| 0.0.6 | 16 / 16 | |
| 0.0.5 | 16 / 16 | |
| 0.0.4 | 16 / 16 | |
| 0.0.3 | 16 / 18 |
v0.0.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.