← Home

@browserless/function

Execute arbitrary JavaScript code in a secure browser sandbox with access to page DOM and network.

69
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

kikobeats

Keywords

browserlesschromeexecutionfunctionheadlessisolatejavascriptpuppeteersandboxserverlessvm

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): Trusted long-standing publisher; missing gitHead is a publish-env change, not a security risk for this package. ai
phantom-deps phantom-dep:p-retry AI (phantom-deps): p-retry is a declared runtime dependency in package.json; phantom-dep heuristic misfires here. ai

Versions (showing 69 of 69)

Version Deps Published
13.6.8 6 / 3
13.6.7 6 / 3
13.6.5 6 / 3
13.6.4 6 / 3
13.6.3 6 / 3
13.6.2 6 / 3
13.1.7 6 / 3
13.1.6 6 / 3
13.1.5 6 / 3
13.1.3 6 / 3
13.1.2 6 / 3
13.1.1 6 / 3
13.0.8 6 / 3
13.0.6 6 / 3
13.0.5 6 / 3
13.0.4 6 / 3
13.0.3 6 / 3
13.0.2 6 / 3
13.0.1 5 / 3
13.0.0 5 / 3
12.0.0 5 / 3
11.0.0 5 / 3
10.12.15 5 / 3
10.12.14 3 / 5
10.12.12 3 / 5
10.12.11 3 / 5
10.12.9 3 / 5
10.12.6 3 / 5
10.12.2 3 / 5
10.12.1 3 / 5
10.11.4 3 / 5
10.11.3 3 / 5
10.11.1 3 / 5
10.10.2 3 / 5
10.10.1 3 / 5
10.9.18 3 / 5
10.9.16 3 / 5
10.9.15 3 / 5
10.9.14 3 / 5
10.9.12 3 / 5
10.9.11 3 / 5
10.9.10 3 / 5
10.9.9 3 / 5
10.9.8 3 / 5
10.9.7 3 / 5
10.9.3 3 / 5
10.9.0 3 / 5
10.8.0 3 / 6
10.7.13 3 / 6
10.7.11 3 / 6
10.7.10 3 / 6
10.7.9 3 / 6
10.7.8 3 / 6
10.7.7 3 / 6
10.7.6 3 / 6
10.7.5 3 / 6
10.7.4 3 / 6
10.7.3 3 / 6
10.7.2 3 / 6
10.7.1 3 / 6
10.7.0 3 / 6
10.6.3 3 / 6
10.6.2 3 / 6
10.6.1 3 / 4
10.6.0 3 / 4
10.5.4 9 / 4
10.5.3 9 / 4
10.5.2 9 / 4
10.5.1 9 / 4

v13.6.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.6.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.6.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.6.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.6.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v13.6.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.7.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.7.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.7.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.7.6

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.7.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.7.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.7.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.7.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.7.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.6.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.6.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.6.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.5.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.5.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.5.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.5.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.