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, so a manually published version cannot be tied back to a reviewed commit.
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 22 of 122)
| Version | Deps | Published |
|---|---|---|
| 10.2.0 | 11 / 4 | |
| 10.1.18 | 11 / 4 | |
| 10.1.17 | 11 / 4 | |
| 10.1.16 | 11 / 4 | |
| 10.1.15 | 11 / 4 | |
| 10.1.14 | 11 / 4 | |
| 10.1.13 | 11 / 4 | |
| 10.1.12 | 11 / 4 | |
| 10.1.11 | 11 / 4 | |
| 10.1.10 | 11 / 4 | |
| 10.1.9 | 11 / 4 | |
| 10.1.8 | 11 / 4 | |
| 10.1.7 | 11 / 4 | |
| 10.1.6 | 11 / 4 | |
| 10.1.5 | 11 / 4 | |
| 10.1.4 | 11 / 4 | |
| 10.1.3 | 11 / 4 | |
| 10.1.1 | 11 / 4 | |
| 10.1.0 | 11 / 4 | |
| 10.0.2 | 11 / 4 | |
| 10.0.1 | 11 / 4 | |
| 10.0.0 | 11 / 5 |
v10.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.17
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v10.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.