@tachybase/plugin-field-markdown-vditor
Used to store Markdown and render it using Vditor editor, supports common Markdown syntax such as list, code, quote, etc., and supports uploading images, recordings, etc.It also allows for instant rendering, where what you see is what you get.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.6.24 | 0 / 9 | |
| 1.6.23 | 0 / 9 | |
| 1.6.22 | 0 / 9 | |
| 1.6.21 | 0 / 9 | |
| 1.6.20 | 0 / 9 | |
| 1.6.19 | 0 / 9 | |
| 1.6.18 | 0 / 9 | |
| 1.6.17 | 0 / 9 | |
| 1.6.16 | 0 / 9 | |
| 1.6.15 | 0 / 9 | |
| 1.6.14 | 0 / 9 | |
| 1.6.7 | 0 / 9 | |
| 1.6.6 | 0 / 9 | |
| 1.6.5 | 0 / 9 | |
| 1.6.4 | 0 / 9 | |
| 1.6.3 | 0 / 9 | |
| 1.6.1 | 0 / 9 | |
| 1.6.0 | 0 / 9 | |
| 1.5.1 | 0 / 9 | |
| 1.5.0 | 0 / 9 | |
| 1.4.0 | 0 / 9 |
v1.6.24
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.23
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.