@pangtou/material-element-plus
`pt-render` 的 Element Plus 物料层。
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 |
|---|---|---|---|---|
| source-diff | net-exec-file:dist/editor-OC8NeJ8Y.cjs | AI (source-diff): Bundled @wangeditor/editor output, not a dropper; net+exec are library boilerplate. | ai | |
| source-diff | net-exec-file:dist/editor-BGUAFRcY.js | AI (source-diff): Vite bundle of wangeditor esm; minified build artifact. | ai | |
| source-diff | obfuscated-file:dist/editor-BGUAFRcY.js | AI (source-diff): File is a bundled copy of @wangeditor/editor with source region comments; long lines are standard bundler output, not intentional obfuscation. | ai | |
| source-diff | obfuscated-file:dist/editor-OC8NeJ8Y.cjs | AI (source-diff): CJS counterpart of the same wangeditor bundle; same rationale as the ESM file. | ai | |
| dependencies | unvetted-dep:md-editor-v3 | AI (dependencies): md-editor-v3 is a known Vue 3 markdown editor; its use here is consistent with a UI component library. | ai | |
| provenance | no-provenance | AI (provenance): No provenance is common (~88% of npm packages); no other risk signals present to elevate this. | ai |
Versions (showing 39 of 39)
| Version | Deps | Published |
|---|---|---|
| 1.1.12 | 5 / 4 | |
| 1.1.8 | 5 / 4 | |
| 1.1.7 | 5 / 4 | |
| 1.1.6 | 5 / 4 | |
| 1.1.5 | 5 / 4 | |
| 1.1.4 | 5 / 4 | |
| 1.1.3 | 5 / 4 | |
| 1.1.2 | 5 / 4 | |
| 1.1.1 | 5 / 4 | |
| 1.1.0 | 5 / 4 | |
| 1.0.28 | 5 / 4 | |
| 1.0.27 | 6 / 4 | |
| 1.0.26 | 6 / 4 | |
| 1.0.25 | 6 / 4 | |
| 1.0.24 | 6 / 4 | |
| 1.0.23 | 6 / 4 | |
| 1.0.22 | 6 / 4 | |
| 1.0.21 | 6 / 4 | |
| 1.0.20 | 6 / 4 | |
| 1.0.19 | 6 / 4 | |
| 1.0.18 | 6 / 4 | |
| 1.0.17 | 6 / 4 | |
| 1.0.16 | 6 / 4 | |
| 1.0.15 | 6 / 4 | |
| 1.0.14 | 6 / 4 | |
| 1.0.13 | 6 / 4 | |
| 1.0.12 | 6 / 4 | |
| 1.0.11 | 6 / 4 | |
| 1.0.10 | 6 / 4 | |
| 1.0.9 | 6 / 4 | |
| 1.0.8 | 6 / 4 | |
| 1.0.7 | 6 / 4 | |
| 1.0.6 | 6 / 3 | |
| 1.0.5 | 6 / 3 | |
| 1.0.4 | 5 / 3 | |
| 1.0.3 | 5 / 3 | |
| 1.0.2 | 5 / 3 | |
| 1.0.1 | 5 / 3 | |
| 1.0.0 | 5 / 3 |
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.26
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.25
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.24
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.22
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.