browserless
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Long-established package; lack of Sigstore attestation is a process gap, not a security risk for this publisher. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): @browserless/capture is a first-party scoped dep from the same monorepo; not a suspicious third-party addition. | ai | |
| dependencies | unvetted-dep:require-one-of | AI (dependencies): Tiny utility; consistent with package's historical deps. | ai | |
| dependencies | unvetted-dep:@browserless/pdf | AI (dependencies): First-party scoped package from same monorepo. | ai | |
| dependencies | unvetted-dep:@browserless/goto | AI (dependencies): First-party scoped package from same monorepo. | ai | |
| dependencies | unvetted-dep:superlock | AI (dependencies): Small utility dep consistent with this package's long-standing dependency set. | ai | |
| dependencies | unvetted-dep:@browserless/errors | AI (dependencies): First-party scoped package from same monorepo. | ai | |
| dependencies | unvetted-dep:@browserless/screenshot | AI (dependencies): First-party scoped package from same monorepo. | ai | |
| dependencies | unvetted-dep:kill-process-group | AI (dependencies): Process management utility; consistent with headless browser use case. | ai | |
| dependencies | unvetted-dep:debug-logfmt | AI (dependencies): Logging utility from same ecosystem; stable dependency. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 13.1.1 | 11 / 5 | |
| 13.1.0 | 11 / 5 | |
| 13.0.9 | 11 / 5 | |
| 13.0.8 | 11 / 5 | |
| 13.0.7 | 11 / 5 | |
| 13.0.0 | 11 / 5 | |
| 12.0.0 | 11 / 5 | |
| 11.0.0 | 11 / 5 | |
| 10.12.15 | 11 / 5 | |
| 10.12.14 | 11 / 5 | |
| 10.12.13 | 11 / 5 | |
| 10.12.12 | 11 / 5 | |
| 10.12.11 | 11 / 5 | |
| 10.12.10 | 11 / 5 | |
| 10.12.9 | 11 / 5 | |
| 10.12.8 | 11 / 5 | |
| 10.12.7 | 11 / 5 | |
| 10.12.6 | 11 / 5 | |
| 10.12.5 | 11 / 5 | |
| 10.12.4 | 11 / 5 | |
| 10.12.3 | 11 / 5 | |
| 10.12.1 | 11 / 5 | |
| 10.12.0 | 11 / 5 | |
| 10.11.4 | 11 / 4 | |
| 10.11.3 | 11 / 4 | |
| 10.11.2 | 11 / 4 | |
| 10.11.1 | 12 / 4 | |
| 10.11.0 | 12 / 4 | |
| 10.10.3 | 11 / 4 | |
| 10.10.2 | 11 / 4 | |
| 10.10.1 | 11 / 4 | |
| 10.10.0 | 11 / 4 | |
| 10.9.18 | 11 / 4 | |
| 10.9.17 | 11 / 4 | |
| 10.9.16 | 11 / 4 | |
| 10.9.15 | 11 / 4 | |
| 10.9.14 | 11 / 4 | |
| 10.9.13 | 11 / 4 | |
| 10.9.11 | 11 / 4 | |
| 10.9.8 | 11 / 4 | |
| 10.9.7 | 11 / 4 | |
| 10.9.6 | 11 / 4 | |
| 10.9.5 | 11 / 4 | |
| 10.9.4 | 11 / 4 | |
| 10.9.2 | 11 / 4 | |
| 10.9.1 | 11 / 4 | |
| 10.9.0 | 11 / 4 | |
| 10.8.0 | 11 / 4 | |
| 10.7.13 | 11 / 4 | |
| 10.7.11 | 11 / 4 | |
| 10.7.10 | 11 / 4 |
v13.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.12.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.11.0
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: kikobeats.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.9.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.8.0
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: kikobeats.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v10.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.