@platejs/utils MIT 19 versions

@platejs/utils

npm Repository Homepage

Plate utils

19

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

zbeyens

Keywords

platepluginslate

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
phantom-deps	phantom-dep:@udecode/react-utils	AI (phantom-deps): @udecode/react-utils is a sibling package in the same monorepo; phantom detection is a false positive in this context.	ai	2026/04/27
publish-pattern	new-deps-added	AI (publish-pattern): react-compiler-runtime is the official Meta/Facebook React compiler runtime; its addition is a legitimate ecosystem adoption, not a supply-chain risk.	ai	2026/04/27
phantom-deps	phantom-dep:clsx	AI (phantom-deps): clsx is a well-known utility; phantom detection likely reflects monorepo build indirection rather than a real risk.	ai	2026/04/27
phantom-deps	phantom-dep:lodash	AI (phantom-deps): lodash is a well-known utility; phantom detection likely reflects monorepo build indirection rather than a real risk.	ai	2026/04/27
dependencies	unvetted-dep:@platejs/core	AI (dependencies): Sibling package from the same udecode/plate monorepo and publisher; unvetted status reflects pipeline lag, not a security concern.	ai	2026/04/25
dependencies	unvetted-dep:@platejs/slate	AI (dependencies): Sibling package from the same udecode/plate monorepo and publisher; unvetted status reflects pipeline lag, not a security concern.	ai	2026/04/25
dependencies	unvetted-dep:@udecode/utils	AI (dependencies): Part of the udecode ecosystem from the same publisher; not a third-party unknown dependency.	ai	2026/04/25
dependencies	unvetted-dep:@udecode/react-utils	AI (dependencies): Part of the udecode ecosystem from the same publisher; not a third-party unknown dependency.	ai	2026/04/25

Versions (showing 19 of 19)

Version	Deps	Published
53.0.7	7 / 1	2026-06-03
53.0.6	7 / 1	2026-05-27
53.0.5	7 / 1	2026-05-21
53.0.3	7 / 1	2026-04-29
53.0.0	7 / 1	2026-04-23
52.3.21	7 / 1	2026-04-01
52.3.16	7 / 1	2026-03-28
52.3.11	7 / 1	2026-03-26
52.3.4	7 / 1	2026-03-11
52.3.2	7 / 3	2026-02-26
52.0.17	7 / 0	2026-01-09
52.0.15	7 / 0	2025-12-15
52.0.11	7 / 0	2025-12-12
52.0.10	6 / 0	2025-12-10
52.0.8	6 / 0	2025-12-03
52.0.1	6 / 0	2025-11-24
52.0.0	6 / 0	2025-11-23
51.1.3	6 / 0	2025-11-20
51.1.2	6 / 0	2025-11-20

v53.0.7

1 finding

LOW No provenance attestation provenance

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

v53.0.6

1 finding

LOW No provenance attestation provenance

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

v53.0.5

1 finding

LOW No provenance attestation provenance

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

v53.0.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.

v52.3.21

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.

v52.3.16

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.

v52.3.11

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.

v52.3.4

1 finding

LOW No provenance attestation provenance

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

v52.3.2

1 finding

LOW No provenance attestation provenance

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

v52.0.17

1 finding

LOW No provenance attestation provenance

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

v52.0.15

1 finding

LOW No provenance attestation provenance

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

v52.0.11

1 finding

LOW No provenance attestation provenance

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

v52.0.10

1 finding

LOW No provenance attestation provenance

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

v52.0.8

1 finding

LOW No provenance attestation provenance

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

v52.0.1

1 finding

LOW No provenance attestation provenance

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

v52.0.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.

v51.1.3

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.

v51.1.2

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.