@tailor-cms/ce-html-manifest
Tailor CMS HTML editor manifest
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 2.0.0 | 1 / 3 | |
| 0.2.1 | 0 / 4 | |
| 0.2.0 | 0 / 4 | |
| 0.1.6 | 0 / 4 | |
| 0.1.5 | 0 / 4 | |
| 0.1.4 | 0 / 4 | |
| 0.1.3 | 0 / 4 | |
| 0.1.2 | 0 / 4 | |
| 0.1.1 | 0 / 4 | |
| 0.1.0 | 0 / 4 | |
| 0.0.15 | 0 / 3 | |
| 0.0.14 | 0 / 3 |
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.