@ctzy-web-client/plugin-component-vue
web client 通用ui库
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:quill | AI (dependencies): quill is a well-known rich-text editor; stable dependency for this UI component library. | ai | |
| dependencies | unvetted-dep:@ctzy-web-client/web-base-client-vue | AI (dependencies): Internal workspace dependency within the same @ctzy-web-client org; not an external risk. | ai | |
| phantom-deps | phantom-dep:@ctzy-web-client/web-base-client-vue | AI (phantom-deps): Same-org workspace dep; phantom-dep heuristic not meaningful here. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): dayjs is declared in dependencies and used transitively; phantom-dep is a false positive for this package. | ai | |
| phantom-deps | phantom-dep:tinymce | AI (phantom-deps): tinymce is declared in dependencies and used via @tinymce/tinymce-vue; phantom-dep is a false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.0.47 | 11 / 3 | |
| 1.0.44 | 11 / 3 | |
| 1.0.39 | 11 / 3 | |
| 1.0.38 | 11 / 3 | |
| 1.0.37 | 11 / 3 | |
| 1.0.34 | 11 / 3 | |
| 1.0.29 | 11 / 3 | |
| 1.0.26 | 11 / 3 | |
| 1.0.25 | 11 / 3 | |
| 1.0.24 | 11 / 3 | |
| 1.0.23 | 10 / 3 | |
| 1.0.11 | 10 / 3 | |
| 1.0.7 | 10 / 3 | |
| 1.0.6 | 10 / 3 | |
| 1.0.3 | 10 / 3 | |
| 1.0.2 | 10 / 3 | |
| 1.0.1 | 10 / 3 |
v1.0.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.39
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: liyufengzhenshuai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: liyufengzhenshuai.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.37
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.