@certd/plugin-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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:baidu-aip-sdk | AI (dependencies): Official Baidu AI SDK; expected dependency for a plugin-plus package integrating Baidu cloud services. | ai | |
| dependencies | unvetted-dep:@baiducloud/sdk | AI (dependencies): Official Baidu Cloud SDK; expected for this package's cloud integration scope. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo plugin package; missing description is consistent across all versions. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Established @certd org plugin package; sparse metadata is consistent across all versions, not indicative of spam/malware. | ai | |
| phantom-deps | phantom-dep:jsencrypt | AI (phantom-deps): Cloud SDK plugin; deps loaded conditionally per provider. | ai | |
| phantom-deps | phantom-dep:baidu-aip-sdk | AI (phantom-deps): Cloud SDK plugin; deps loaded conditionally per provider. | ai | |
| phantom-deps | phantom-dep:cos-nodejs-sdk-v5 | AI (phantom-deps): Cloud SDK plugin; deps loaded conditionally per provider. | ai | |
| phantom-deps | phantom-dep:https-proxy-agent | AI (phantom-deps): Cloud SDK plugin; deps loaded conditionally per provider. | ai | |
| phantom-deps | phantom-dep:@alicloud/pop-core | AI (phantom-deps): Cloud SDK plugin; deps loaded conditionally per provider. | ai | |
| phantom-deps | phantom-dep:tencentcloud-sdk-nodejs | AI (phantom-deps): Cloud SDK plugin; deps loaded conditionally per provider. | ai | |
| phantom-deps | phantom-dep:@baiducloud/sdk | AI (phantom-deps): Cloud SDK plugin; deps loaded conditionally per provider. | ai | |
| phantom-deps | phantom-dep:qiniu | AI (phantom-deps): Cloud SDK plugin; deps loaded conditionally per provider, not statically imported. | ai | |
| phantom-deps | phantom-dep:ali-oss | AI (phantom-deps): Cloud SDK plugin; deps loaded conditionally per provider. | ai | |
| phantom-deps | phantom-dep:basic-ftp | AI (phantom-deps): Cloud SDK plugin; deps loaded conditionally per provider. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Monorepo plugin; dayjs likely used transitively or in bundled output, stable FP. | ai | |
| phantom-deps | phantom-dep:@certd/plus-core | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable FP for this monorepo package. | ai | |
| phantom-deps | phantom-dep:querystring | AI (phantom-deps): Monorepo plugin; querystring likely used transitively or in bundled output, stable FP. | ai | |
| phantom-deps | phantom-dep:form-data | AI (phantom-deps): Monorepo plugin; form-data likely used transitively or in bundled output, stable FP. | ai |
Versions (showing 76 of 176)
| Version | Deps | Published |
|---|---|---|
| 1.34.7 | 21 / 19 | |
| 1.34.6 | 21 / 19 | |
| 1.34.5 | 21 / 19 | |
| 1.34.4 | 21 / 19 | |
| 1.34.3 | 21 / 19 | |
| 1.34.2 | 19 / 19 | |
| 1.34.1 | 19 / 19 | |
| 1.34.0 | 19 / 19 | |
| 1.33.8 | 19 / 19 | |
| 1.33.7 | 19 / 19 | |
| 1.33.6 | 19 / 19 | |
| 1.33.5 | 19 / 19 | |
| 1.33.4 | 19 / 19 | |
| 1.33.3 | 19 / 19 | |
| 1.33.2 | 19 / 19 | |
| 1.33.1 | 19 / 19 | |
| 1.33.0 | 19 / 19 | |
| 1.32.0 | 19 / 19 | |
| 1.31.11 | 19 / 19 | |
| 1.31.10 | 19 / 19 | |
| 1.31.9 | 19 / 19 | |
| 1.31.8 | 19 / 19 | |
| 1.31.7 | 19 / 19 | |
| 1.31.6 | 19 / 19 | |
| 1.31.5 | 19 / 19 | |
| 1.31.4 | 19 / 19 | |
| 1.31.3 | 19 / 19 | |
| 1.31.2 | 19 / 17 | |
| 1.31.1 | 19 / 17 | |
| 1.31.0 | 19 / 17 | |
| 1.30.6 | 19 / 17 | |
| 1.30.5 | 19 / 17 | |
| 1.30.3 | 19 / 17 | |
| 1.30.2 | 17 / 17 | |
| 1.30.1 | 17 / 17 | |
| 1.30.0 | 17 / 17 | |
| 1.29.5 | 17 / 17 | |
| 1.29.4 | 17 / 17 | |
| 1.29.3 | 17 / 17 | |
| 1.29.2 | 17 / 17 | |
| 1.29.1 | 17 / 17 | |
| 1.29.0 | 17 / 17 | |
| 1.28.4 | 17 / 17 | |
| 1.28.3 | 17 / 17 | |
| 1.28.2 | 17 / 17 | |
| 1.28.1 | 17 / 17 | |
| 1.28.0 | 17 / 17 | |
| 1.27.9 | 16 / 17 | |
| 1.27.8 | 16 / 17 | |
| 1.27.7 | 16 / 17 | |
| 1.27.6 | 16 / 17 | |
| 1.27.5 | 16 / 17 | |
| 1.27.4 | 16 / 17 | |
| 1.27.3 | 16 / 17 | |
| 1.27.2 | 16 / 17 | |
| 1.27.1 | 16 / 19 | |
| 1.27.0 | 14 / 19 | |
| 1.26.16 | 14 / 19 | |
| 1.26.15 | 14 / 19 | |
| 1.26.14 | 14 / 19 | |
| 1.26.13 | 14 / 19 | |
| 1.26.12 | 14 / 19 | |
| 1.26.11 | 12 / 19 | |
| 1.26.10 | 12 / 19 | |
| 1.26.9 | 12 / 19 | |
| 1.26.8 | 11 / 19 | |
| 1.26.7 | 11 / 19 | |
| 1.26.6 | 11 / 19 | |
| 1.26.4 | 11 / 19 | |
| 1.26.3 | 11 / 19 | |
| 1.26.2 | 11 / 19 | |
| 1.26.1 | 11 / 19 | |
| 1.24.3 | 1 / 24 | |
| 1.24.2 | 1 / 24 | |
| 1.24.1 | 0 / 22 | |
| 1.24.0 | 0 / 21 |
v1.33.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.33.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.32.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.30.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.