@builderbot/provider-wppconnect
Now I’m the model of a modern major general / The venerated Virginian veteran whose men are all / Lining up, to put me up on a pedestal / Writin’ letters to relatives / Embellishin’ my elegance and eloquence / But the elephant is in the room / The truth i
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Quirky description and sparse README are a style choice for this monorepo package, not spam indicators. | ai | |
| phantom-deps | phantom-dep:sharp | AI (phantom-deps): sharp is a known runtime/binary implicit dependency; stable for this package. | ai | |
| phantom-deps | phantom-dep:body-parser | AI (phantom-deps): body-parser referenced via config/middleware convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@jest/globals | AI (phantom-deps): Framework-scoped test dependency loaded by convention; stable false positive. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.4.1 | 5 / 21 | |
| 1.4.0 | 5 / 21 | |
| 1.3.15 | 5 / 21 | |
| 1.3.14 | 5 / 21 | |
| 1.3.13 | 5 / 21 | |
| 1.3.12 | 5 / 21 | |
| 1.3.11 | 5 / 21 | |
| 1.3.10 | 5 / 21 | |
| 1.3.8 | 5 / 21 | |
| 1.3.7 | 5 / 21 | |
| 1.3.5 | 5 / 21 | |
| 1.3.4 | 5 / 21 | |
| 1.3.3 | 5 / 21 | |
| 1.3.1 | 5 / 21 | |
| 1.2.9 | 5 / 21 | |
| 1.2.8 | 5 / 21 | |
| 1.2.7 | 5 / 21 | |
| 1.2.6 | 5 / 21 |
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.