browser-env — Greenflagged

Simulates a global browser environment using jsdom

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

lukechilds

Keywords

simulateglobalnodebrowserenvironmentenv

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-takeover	AI (maintainer-change): Transfer from camshaft to lukechilds in 2016 is a documented legitimate handoff. lukechilds is a well-established publisher; repo URL and author field match the new owner consistently.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher change to lukechilds in 2016 is a legitimate transfer. lukechilds has strong npm track record (1118 approved packages) and repo URL matches their GitHub identity.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): lukechilds is the legitimate new owner; well-established publisher with consistent identity across package.json, repo URL, and npm account.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Removal of camshaft is part of the same legitimate 2016 ownership transfer to lukechilds.	ai	2026/04/24
publish-pattern	new-deps-added	AI (publish-pattern): jsdom is the core dependency for a browser environment simulator — its addition is the primary purpose of this package rewrite, not a suspicious injection.	ai	2026/04/24

Versions (showing 40 of 40)

Version	Deps	Published
3.3.0	1 / 5	2019-11-05
3.2.6	1 / 5	2019-02-23
3.2.5	1 / 5	2018-02-06
3.2.4	1 / 5	2017-11-27
3.2.3	1 / 5	2017-11-23
3.2.2	1 / 5	2017-11-03
3.2.1	1 / 5	2017-10-02
3.2.0	1 / 5	2017-08-23
3.1.2	1 / 5	2017-08-10
3.1.1	1 / 5	2017-08-10
3.1.0	1 / 5	2017-07-05
3.0.2	1 / 5	2017-06-30
3.0.1	1 / 5	2017-06-30
3.0.0	1 / 5	2017-06-30
2.0.31	1 / 5	2017-05-03
2.0.30	1 / 5	2017-04-10
2.0.29	1 / 5	2017-04-03
2.0.28	1 / 5	2017-04-01
2.0.27	1 / 5	2017-03-29
2.0.26	1 / 5	2017-03-27
2.0.25	1 / 5	2017-03-10
2.0.24	1 / 5	2017-03-05
2.0.23	1 / 5	2017-03-04
2.0.22	1 / 5	2017-03-02
2.0.21	2 / 5	2017-02-12
2.0.20	2 / 5	2017-02-06
2.0.19	2 / 5	2016-12-19
2.0.18	2 / 5	2016-12-19
2.0.16	2 / 5	2016-11-15
2.0.15	2 / 5	2016-10-25
2.0.14	2 / 5	2016-10-24
2.0.13	2 / 5	2016-10-24
2.0.12	2 / 5	2016-10-17
2.0.11	2 / 5	2016-10-12
2.0.10	2 / 8	2016-10-12
2.0.9	1 / 8	2016-10-04
2.0.8	1 / 8	2016-10-04
0.1.2	0 / 2	2013-02-15
0.1.1	0 / 2	2013-02-11
0.1.0	0 / 2	2013-02-08

v3.3.0

1 finding

LOW No provenance attestation provenance

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

v3.2.6

1 finding

LOW No provenance attestation provenance

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

v3.2.5

1 finding

LOW No provenance attestation provenance

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

v3.2.4

1 finding

LOW No provenance attestation provenance

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

v3.2.3

1 finding

LOW No provenance attestation provenance

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

v3.2.2

1 finding

LOW No provenance attestation provenance

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

v3.2.1

1 finding

LOW No provenance attestation provenance

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

v3.2.0

1 finding

LOW No provenance attestation provenance

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

v3.1.2

1 finding

LOW No provenance attestation provenance

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

v3.1.1

1 finding

LOW No provenance attestation provenance

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

v3.1.0

1 finding

LOW No provenance attestation provenance

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

v3.0.2

1 finding

LOW No provenance attestation provenance

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

v3.0.1

1 finding

LOW No provenance attestation provenance

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

v3.0.0

1 finding

LOW No provenance attestation provenance

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

v2.0.31

1 finding

LOW No provenance attestation provenance

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

v2.0.30

1 finding

LOW No provenance attestation provenance

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

v2.0.29

1 finding

LOW No provenance attestation provenance

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

v2.0.28

1 finding

LOW No provenance attestation provenance

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

v2.0.27

1 finding

LOW No provenance attestation provenance

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

v2.0.26

1 finding

LOW No provenance attestation provenance

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

v2.0.25

1 finding

LOW No provenance attestation provenance

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

v2.0.24

1 finding

LOW No provenance attestation provenance

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

v2.0.23

1 finding

LOW No provenance attestation provenance

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

v2.0.22

1 finding

LOW No provenance attestation provenance

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

v2.0.21

1 finding

LOW No provenance attestation provenance

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

v2.0.20

1 finding

LOW No provenance attestation provenance

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

v2.0.19

1 finding

LOW No provenance attestation provenance

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

v2.0.18

1 finding

LOW No provenance attestation provenance

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

v2.0.16

1 finding

LOW No provenance attestation provenance

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

v2.0.15

1 finding

LOW No provenance attestation provenance

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

v2.0.14

1 finding

LOW No provenance attestation provenance

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

v2.0.13

1 finding

LOW No provenance attestation provenance

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

v2.0.12

1 finding

LOW No provenance attestation provenance

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

v2.0.11

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (camshaft) were replaced by new maintainers (lukechilds). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: camshaft → lukechilds (on 2016-10-12) provenance

This version was published by a different npm account than previous versions on 2016-10-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.10

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (camshaft) were replaced by new maintainers (lukechilds). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: camshaft → lukechilds (on 2016-10-12) provenance

This version was published by a different npm account than previous versions on 2016-10-12. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.9

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (camshaft) were replaced by new maintainers (lukechilds). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: camshaft → lukechilds (on 2016-10-04) provenance

This version was published by a different npm account than previous versions on 2016-10-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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

v2.0.8

3 findings

HIGH Complete maintainer takeover detected maintainer-change

All previous maintainers (camshaft) were replaced by new maintainers (lukechilds). This is a strong signal of a potential package hijack and requires careful review.

HIGH Publisher changed: camshaft → lukechilds (on 2016-10-04) provenance

This version was published by a different npm account than previous versions on 2016-10-04. This could indicate a legitimate maintainer transition or an account compromise.

LOW No provenance attestation provenance

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