@certd/plugin-lib
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 |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is an official Alibaba Cloud SDK utility, consistent with existing alicloud deps in this package. | ai | |
| provenance | no-provenance | AI (provenance): Only ~12% of npm packages have provenance; not a disqualifier for established packages. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Established package with long history; missing description is metadata gap, not malware signal. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established @certd org package; missing metadata is a style issue, not a malice indicator. | ai | |
| dependencies | unvetted-dep:@alicloud/openapi-client | AI (dependencies): Official Alibaba Cloud SDK client; expected for cloud provider integration. | ai | |
| dependencies | unvetted-dep:qiniu | AI (dependencies): Qiniu is a legitimate Chinese cloud storage SDK; expected dependency for a cert deployment plugin. | ai | |
| dependencies | unvetted-dep:@alicloud/openapi-util | AI (dependencies): Official Alibaba Cloud SDK utility; expected for cloud provider integration. | ai | |
| phantom-deps | phantom-dep:strip-ansi | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:@certd/plus-core | AI (phantom-deps): Same-org package; phantom-dep is a false positive for monorepo structures. | ai | |
| phantom-deps | phantom-dep:cos-nodejs-sdk-v5 | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:socks-proxy-agent | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:@alicloud/pop-core | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:ssh2 | AI (phantom-deps): Plugin-lib re-exports cloud/infra SDKs; phantom-dep pattern is structural, not a risk. | ai | |
| phantom-deps | phantom-dep:@aws-sdk/client-s3 | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:@alicloud/openapi-util | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:@kubernetes/client-node | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:tencentcloud-sdk-nodejs | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:@alicloud/openapi-client | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:@alicloud/tea-util | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:qiniu | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:socks | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:ali-oss | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:basic-ftp | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai | |
| phantom-deps | phantom-dep:iconv-lite | AI (phantom-deps): Cloud SDK re-export pattern; stable for this package. | ai |
Versions (showing 48 of 148)
| Version | Deps | Published |
|---|---|---|
| 1.34.7 | 20 / 13 | |
| 1.34.6 | 20 / 13 | |
| 1.34.5 | 18 / 13 | |
| 1.34.4 | 18 / 13 | |
| 1.34.3 | 18 / 13 | |
| 1.34.2 | 18 / 13 | |
| 1.34.1 | 18 / 13 | |
| 1.34.0 | 18 / 13 | |
| 1.33.8 | 18 / 13 | |
| 1.33.7 | 17 / 13 | |
| 1.33.6 | 17 / 13 | |
| 1.33.5 | 17 / 13 | |
| 1.33.4 | 17 / 13 | |
| 1.33.3 | 17 / 13 | |
| 1.33.2 | 17 / 13 | |
| 1.33.1 | 17 / 13 | |
| 1.33.0 | 17 / 13 | |
| 1.32.0 | 17 / 13 | |
| 1.31.11 | 17 / 13 | |
| 1.31.10 | 17 / 13 | |
| 1.31.9 | 17 / 13 | |
| 1.31.8 | 17 / 13 | |
| 1.31.7 | 17 / 13 | |
| 1.31.6 | 17 / 13 | |
| 1.31.5 | 17 / 13 | |
| 1.31.4 | 17 / 13 | |
| 1.31.3 | 17 / 13 | |
| 1.31.2 | 17 / 13 | |
| 1.31.1 | 17 / 13 | |
| 1.31.0 | 17 / 13 | |
| 1.30.6 | 17 / 13 | |
| 1.30.5 | 17 / 13 | |
| 1.30.3 | 17 / 13 | |
| 1.30.2 | 17 / 13 | |
| 1.30.1 | 17 / 13 | |
| 1.30.0 | 17 / 13 | |
| 1.29.5 | 17 / 13 | |
| 1.29.4 | 17 / 13 | |
| 1.29.3 | 17 / 13 | |
| 1.29.2 | 13 / 13 | |
| 1.29.1 | 13 / 13 | |
| 1.29.0 | 13 / 13 | |
| 1.28.4 | 13 / 13 | |
| 1.28.3 | 13 / 13 | |
| 1.28.2 | 13 / 13 | |
| 1.28.1 | 13 / 13 | |
| 1.28.0 | 13 / 13 | |
| 1.27.9 | 13 / 13 |
v1.33.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.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.
v1.32.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.
v1.31.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.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.
v1.30.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.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.
v1.29.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.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.
v1.28.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.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.
v1.27.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.