@browserless/screenshot
Capture high-quality screenshots of websites with overlay support, device emulation, and automated image optimization.
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 | missing-githead | AI (provenance): Long-established package with clean diff; missing gitHead alone is insufficient to block for this publisher. | ai | |
| provenance | no-provenance | AI (provenance): Long-established package from trusted publisher; lack of Sigstore attestation is not a security risk here. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is explicitly declared as a direct dependency in package.json; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 13.0.9 | 17 / 3 | |
| 13.0.8 | 17 / 3 | |
| 13.0.7 | 17 / 3 | |
| 13.0.0 | 17 / 3 | |
| 12.0.0 | 17 / 3 | |
| 11.0.0 | 17 / 3 | |
| 10.12.15 | 17 / 3 | |
| 10.12.14 | 17 / 3 | |
| 10.12.13 | 17 / 3 | |
| 10.12.11 | 17 / 3 | |
| 10.12.10 | 17 / 3 | |
| 10.12.8 | 17 / 3 | |
| 10.12.7 | 17 / 3 | |
| 10.12.6 | 17 / 3 | |
| 10.12.5 | 17 / 3 | |
| 10.12.4 | 17 / 3 | |
| 10.12.3 | 16 / 3 | |
| 10.11.4 | 16 / 3 | |
| 10.11.3 | 16 / 3 | |
| 10.11.1 | 16 / 3 | |
| 10.11.0 | 16 / 3 | |
| 10.10.3 | 16 / 3 | |
| 10.10.2 | 16 / 3 | |
| 10.10.1 | 17 / 3 | |
| 10.10.0 | 17 / 3 | |
| 10.9.18 | 17 / 3 | |
| 10.9.17 | 16 / 3 | |
| 10.9.16 | 16 / 3 | |
| 10.9.15 | 16 / 3 | |
| 10.9.14 | 16 / 3 | |
| 10.9.13 | 16 / 3 | |
| 10.9.11 | 16 / 3 | |
| 10.9.8 | 16 / 3 | |
| 10.9.7 | 16 / 3 | |
| 10.9.6 | 16 / 3 | |
| 10.9.5 | 15 / 3 | |
| 10.9.4 | 15 / 3 | |
| 10.9.2 | 15 / 3 | |
| 10.9.1 | 15 / 3 | |
| 10.9.0 | 15 / 3 | |
| 10.8.0 | 15 / 3 | |
| 10.7.13 | 15 / 3 | |
| 10.7.11 | 15 / 3 | |
| 10.7.10 | 14 / 3 |
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
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.
[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.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.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.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.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.