@wangeditor/core
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 |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @wangeditor/core is the core module of the wangEditor editor project, not a typosquat of cors. | ai | |
| phantom-deps | phantom-dep:html-void-elements | AI (phantom-deps): Declared runtime dependency; phantom-dep heuristic misfires on indirect/bundled usage. | ai | |
| phantom-deps | phantom-dep:scroll-into-view-if-needed | AI (phantom-deps): Declared runtime dependency; phantom-dep heuristic misfires on indirect/bundled usage. | ai | |
| phantom-deps | phantom-dep:@types/event-emitter | AI (phantom-deps): Type-only dependency; not directly imported at runtime by design. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 1.1.19 | 6 / 1 | |
| 1.1.18 | 6 / 1 | |
| 1.1.17 | 6 / 1 | |
| 1.1.16 | 6 / 1 | |
| 1.1.15 | 6 / 1 | |
| 1.1.14 | 6 / 1 | |
| 1.1.13 | 6 / 1 | |
| 1.1.12 | 6 / 1 | |
| 1.1.11 | 6 / 1 | |
| 1.1.10 | 6 / 1 | |
| 1.1.9 | 6 / 1 | |
| 1.1.8 | 6 / 1 | |
| 1.1.7 | 6 / 1 | |
| 1.1.6 | 6 / 1 | |
| 1.1.5 | 6 / 1 | |
| 1.1.4 | 6 / 1 | |
| 1.1.3 | 6 / 1 | |
| 1.1.2 | 6 / 1 | |
| 1.1.1 | 6 / 1 | |
| 1.1.0 | 6 / 1 | |
| 1.0.1 | 6 / 1 | |
| 1.0.0 | 6 / 1 |
v1.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.