@mekari/pixel-rich-text-editor
Mekari Pixel | Rich text editor based Quill.js
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers follow Mekari naming conventions; consistent with org-internal team expansion across versions. | ai | |
| dependencies | unvetted-dep:quill | AI (dependencies): Quill is a well-known open-source rich text editor; stable dependency for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established internal Mekari design-system package; provenance absence is consistent across all versions. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.4.6 | 4 / 1 | |
| 0.4.5 | 4 / 1 | |
| 0.4.4 | 4 / 1 | |
| 0.4.3 | 4 / 1 | |
| 0.4.2 | 4 / 1 | |
| 0.4.1 | 4 / 1 | |
| 0.4.0 | 4 / 1 | |
| 0.3.0 | 3 / 1 | |
| 0.2.0 | 3 / 1 |
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.