@oneplatformdev/plate MIT 27 versions

@oneplatformdev/plate

npm Repository Homepage

Plate.js v53 rich-text editor preconfigured for OnePlatform apps

27

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

oneplatformdev

Keywords

plateplatejseditorrich-textreactwysiwygslateoneplatform

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@uploadthing/react	AI (phantom-deps): Uploadthing ecosystem; re-exported or used indirectly; stable false positive.	ai	2026/05/28
phantom-deps	phantom-dep:sonner	AI (phantom-deps): Re-exported or used indirectly via @udecode/plate ecosystem; stable false positive for this package.	ai	2026/05/28
phantom-deps	phantom-dep:slate-hyperscript	AI (phantom-deps): slate-hyperscript is a transitive dep of the plate ecosystem; stable false positive.	ai	2026/05/24
phantom-deps	phantom-dep:slate-dom	AI (phantom-deps): slate-dom is a transitive dep of @udecode/plate-core; declared for consumers, not directly imported.	ai	2026/05/24
phantom-deps	phantom-dep:slate-history	AI (phantom-deps): slate-history is a transitive dep re-exported via @udecode/slate; stable false positive.	ai	2026/05/24
phantom-deps	phantom-dep:pdf-lib	AI (phantom-deps): Declared runtime dep used via dynamic import/config in a rich-text editor; stable false positive for this package.	ai	2026/05/04
phantom-deps	phantom-dep:html2canvas-pro	AI (phantom-deps): Declared runtime dep used via dynamic import/config in a rich-text editor; stable false positive for this package.	ai	2026/05/04

Versions (showing 27 of 27)

Version	Deps	Published
0.1.0	56 / 30	2026-04-30
0.0.54	74 / 29	2026-04-14
0.0.50	74 / 29	2026-02-12
0.0.44	74 / 29	2025-10-08
0.0.43	74 / 29	2025-10-08
0.0.42	74 / 29	2025-10-08
0.0.41	74 / 29	2025-10-02
0.0.40	74 / 29	2025-10-02
0.0.39	74 / 29	2025-10-02
0.0.38	74 / 29	2025-10-02
0.0.37	74 / 29	2025-10-02
0.0.36	74 / 29	2025-10-02
0.0.35	74 / 29	2025-10-02
0.0.34	74 / 30	2025-10-02
0.0.33	73 / 30	2025-10-02
0.0.32	74 / 30	2025-10-02
0.0.31	74 / 31	2025-10-02
0.0.30	74 / 31	2025-10-02
0.0.28	74 / 22	2025-10-02
0.0.25	74 / 20	2025-10-02
0.0.24	74 / 20	2025-10-02
0.0.23	74 / 20	2025-10-01
0.0.22	0 / 0	2025-10-01
0.0.21	0 / 0	2025-10-01
0.0.20	0 / 0	2025-10-01
0.0.19	0 / 0	2025-10-01
0.0.18	0 / 0	2025-10-01

v0.1.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.54

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.50

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.44

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.43

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.42

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.41

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.40

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.39

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.38

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.37

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.36

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.35

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.34

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.33

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.32

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.30

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.28

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.25

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.24

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.23

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.22

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.21

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.20

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.19

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v0.0.18

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.