@ndla/editor
Slate editor plugins for NDLA
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
Keywords
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): Org-wide maintainer rotation across NDLA monorepo packages, publisher has strong track record. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org transition; no takeover behavior evident. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get() used in a Proxy trap inside createSerializer — standard JS pattern, not obfuscation. | ai |
Versions (showing 47 of 47)
| Version | Deps | Published |
|---|---|---|
| 0.0.49 | 6 / 4 | |
| 0.0.47 | 6 / 4 | |
| 0.0.46 | 6 / 4 | |
| 0.0.45 | 6 / 4 | |
| 0.0.44 | 6 / 4 | |
| 0.0.43 | 6 / 4 | |
| 0.0.42 | 6 / 4 | |
| 0.0.41 | 6 / 4 | |
| 0.0.40 | 6 / 4 | |
| 0.0.39 | 6 / 4 | |
| 0.0.38 | 6 / 4 | |
| 0.0.37 | 6 / 4 | |
| 0.0.36 | 6 / 4 | |
| 0.0.35 | 6 / 4 | |
| 0.0.34 | 6 / 4 | |
| 0.0.33 | 6 / 4 | |
| 0.0.32 | 6 / 4 | |
| 0.0.31 | 6 / 4 | |
| 0.0.30 | 6 / 4 | |
| 0.0.29 | 6 / 4 | |
| 0.0.28 | 6 / 4 | |
| 0.0.27 | 6 / 4 | |
| 0.0.26 | 6 / 4 | |
| 0.0.25 | 5 / 3 | |
| 0.0.24 | 5 / 3 | |
| 0.0.23 | 5 / 3 | |
| 0.0.22 | 5 / 3 | |
| 0.0.21 | 5 / 3 | |
| 0.0.20 | 5 / 3 | |
| 0.0.19 | 5 / 3 | |
| 0.0.18 | 5 / 3 | |
| 0.0.17 | 5 / 3 | |
| 0.0.16 | 5 / 3 | |
| 0.0.15 | 5 / 3 | |
| 0.0.14 | 5 / 3 | |
| 0.0.13 | 5 / 3 | |
| 0.0.12 | 5 / 3 | |
| 0.0.11 | 5 / 3 | |
| 0.0.10 | 5 / 3 | |
| 0.0.9 | 5 / 3 | |
| 0.0.8 | 5 / 3 | |
| 0.0.7 | 5 / 3 | |
| 0.0.6 | 5 / 3 | |
| 0.0.5 | 5 / 3 | |
| 0.0.4 | 5 / 3 | |
| 0.0.3 | 5 / 3 | |
| 0.0.2 | 5 / 3 |
v0.0.19
2 findingsThis version was published by a different npm account than previous versions on 2025-04-22. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.