@ndla/editor-components

Slate editor components for NDLA.

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

ndlauserjonasc-knowitgunnarvellejnattenirleamatho

Keywords

editorslatendla

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
dependencies	unvetted-dep:@ndla/editor	AI (dependencies): Same NDLA monorepo sibling; org-internal dependency, not a third-party supply chain risk.	ai	2026/05/27
dependencies	unvetted-dep:@ndla/primitives	AI (dependencies): Same NDLA monorepo sibling; org-internal dependency, not a third-party supply chain risk.	ai	2026/05/27
provenance	no-provenance	AI (provenance): NDLA org packages consistently lack Sigstore provenance; stable false positive for this package family.	ai	2026/05/26

Versions (showing 13 of 13)

Version	Deps	Published
0.0.83	4 / 2	2026-05-07
0.0.82	4 / 2	2026-04-29
0.0.81	4 / 2	2026-04-24
0.0.73	4 / 2	2026-02-17
0.0.72	4 / 2	2026-02-02
0.0.67	4 / 2	2026-01-15
0.0.65	4 / 2	2025-12-12
0.0.58	4 / 2	2025-11-04
0.0.55	4 / 2	2025-10-22
0.0.47	4 / 2	2025-09-16
0.0.43	4 / 2	2025-08-27
0.0.41	4 / 2	2025-08-01
0.0.38	4 / 2	2025-06-18

v0.0.83

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.82

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.81

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.73

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.72

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.67

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.65

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.58

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.55

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.47

1 finding

INFO No provenance attestation provenance

[Accepted risk] 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. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.41

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.38

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.