@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 — 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: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 51 of 98)
| Version | Deps | Published |
|---|---|---|
| 1.41.1 | 9 / 21 | |
| 1.41.0 | 9 / 21 | |
| 1.40.5 | 9 / 21 | |
| 1.40.4 | 9 / 21 | |
| 1.40.3 | 9 / 21 | |
| 1.40.2 | 9 / 21 | |
| 1.40.1 | 9 / 21 | |
| 1.40.0 | 9 / 21 | |
| 1.39.16 | 9 / 21 | |
| 1.39.14 | 9 / 21 | |
| 1.39.13 | 9 / 21 | |
| 1.39.12 | 9 / 18 | |
| 1.39.11 | 9 / 18 | |
| 1.39.10 | 9 / 18 | |
| 1.39.9 | 9 / 18 | |
| 1.39.8 | 9 / 18 | |
| 1.39.7 | 9 / 18 | |
| 1.39.6 | 9 / 18 | |
| 1.39.5 | 9 / 18 | |
| 1.39.4 | 9 / 18 | |
| 1.39.3 | 9 / 18 | |
| 1.39.2 | 9 / 18 | |
| 1.39.1 | 9 / 18 | |
| 1.39.0 | 9 / 18 | |
| 1.38.12 | 9 / 18 | |
| 1.38.11 | 9 / 18 | |
| 1.38.10 | 9 / 18 | |
| 1.38.9 | 9 / 18 | |
| 1.38.8 | 9 / 18 | |
| 1.38.7 | 9 / 18 | |
| 1.38.6 | 9 / 18 | |
| 1.38.5 | 9 / 18 | |
| 1.38.4 | 9 / 18 | |
| 1.38.3 | 9 / 18 | |
| 1.38.2 | 9 / 18 | |
| 1.38.1 | 9 / 18 | |
| 1.38.0 | 7 / 18 | |
| 1.37.17 | 21 / 19 | |
| 1.37.16 | 21 / 19 | |
| 1.37.15 | 21 / 19 | |
| 1.37.14 | 21 / 19 | |
| 1.37.13 | 21 / 19 | |
| 1.37.12 | 21 / 19 | |
| 1.37.11 | 21 / 19 | |
| 1.37.10 | 21 / 19 | |
| 1.37.9 | 21 / 19 | |
| 1.37.8 | 21 / 19 | |
| 1.37.7 | 21 / 19 | |
| 1.37.6 | 21 / 19 | |
| 1.37.5 | 21 / 19 | |
| 1.37.4 | 21 / 19 |
v1.41.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.39.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.37.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.