insert-module-globals — Greenflagged

insert implicit module globals into a module-deps stream

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

lukechildsdefunctzombiesubstackferossgkatsevzertoshmafintoshmaxogdendominictarrthlorenzterinjokesjmmmellowmelonashaffer88baluptoncwmmajprichardsonindutnyjryanssethvincentyoshuawuytsungoldmanahdinosaurelnounchparshapyerkopalmaforbeslindesayleichtgewichtgarannbretanandthakkermattdeslhughskfpereira1goto-bus-stopbpostlethwaiteemilbayesstevemaopkruminstehshrike

Keywords

__filename__dirnameglobalprocessmodule-depsbrowser-packbrowserify

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	publisher-changed	AI (provenance): Publisher change from zertosh to parshap occurred in 2015; parshap is a trusted, long-standing npm publisher and browserify ecosystem collaborator.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): lukechilds and defunctzombie are well-known legitimate Browserify ecosystem contributors; this is a routine org-level maintainer rotation, not a takeover.	ai	2026/04/23
maintainer-change	maintainer-removed	AI (maintainer-change): dcousens removal is part of the same routine Browserify org maintainer rotation; no suspicious pattern.	ai	2026/04/23
bogus-package	bogus-package	AI (bogus-package): Spam flag is tied to historical maintainer 'jmm', not the current publisher. Package is a legitimate, widely-used Browserify core component with 1.3M weekly downloads.	ai	2026/04/23

Versions (showing 64 of 64)

Version	Deps	Published
7.2.1	10 / 7	2020-10-09
7.2.0	10 / 7	2018-06-15
7.1.0	9 / 6	2018-05-16
7.0.6	9 / 5	2018-04-06
7.0.5	8 / 5	2018-03-28
7.0.4	8 / 5	2018-03-21
7.0.3	8 / 5	2018-03-21
7.0.2	8 / 5	2018-02-28
7.0.1	8 / 5	2015-10-31
7.0.0	8 / 5	2015-10-26
6.6.3	8 / 5	2015-10-19
6.6.2	8 / 5	2015-10-18
6.6.1	8 / 5	2015-10-16
6.6.0	8 / 5	2015-09-18
6.5.2	7 / 5	2015-07-04
6.5.1	7 / 4	2015-06-27
6.5.0	7 / 4	2015-05-25
6.4.3	7 / 4	2015-05-20
6.4.2	7 / 4	2015-05-07
6.4.1	7 / 4	2015-05-07
6.4.0	7 / 4	2015-04-27
6.3.0	7 / 4	2015-04-26
6.2.1	7 / 4	2015-02-28
6.2.0	7 / 4	2014-12-31
6.1.0	6 / 4	2014-07-24
6.0.0	6 / 4	2014-05-10
5.0.1	5 / 4	2014-03-28
5.0.0	4 / 4	2014-03-28
4.1.0	5 / 4	2014-03-18
4.0.0	5 / 4	2014-03-05
3.2.0	5 / 4	2014-02-15
3.1.3	5 / 4	2014-02-11
3.1.2	5 / 4	2014-02-01
3.1.1	5 / 4	2014-02-01
3.1.0	5 / 4	2014-02-01
3.0.2	5 / 4	2014-02-01
3.0.1	5 / 4	2014-02-01
3.0.0	5 / 4	2014-01-29
2.3.4	9 / 3	2014-01-26
2.3.3	9 / 3	2014-01-26
2.3.2	9 / 3	2014-01-26
2.3.1	7 / 5	2014-01-26
2.3.0	7 / 5	2013-12-28
2.2.0	7 / 5	2013-12-19
2.1.1	6 / 5	2013-12-15
2.1.0	6 / 5	2013-12-11
2.0.0	6 / 5	2013-12-08
1.3.1	6 / 5	2013-09-23
1.3.0	6 / 5	2013-09-19
1.2.1	6 / 5	2013-08-04
1.2.0	6 / 5	2013-06-24
1.1.2	6 / 5	2013-06-24
1.1.1	6 / 5	2013-06-24
1.1.0	6 / 5	2013-06-23
1.0.2	6 / 5	2013-06-17
1.0.1	6 / 5	2013-06-17
1.0.0	6 / 5	2013-06-10
0.2.1	6 / 5	2013-03-23
0.2.0	7 / 5	2013-03-14
0.1.3	7 / 3	2013-03-07
0.1.2	8 / 2	2013-02-28
0.1.1	7 / 2	2013-02-25
0.1.0	7 / 2	2013-02-22
0.0.1	7 / 2	2013-02-21

v7.2.1

1 finding

LOW No provenance attestation provenance

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

v7.2.0

1 finding

LOW No provenance attestation provenance

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

v7.1.0

1 finding

LOW No provenance attestation provenance

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

v7.0.6

1 finding

LOW No provenance attestation provenance

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

v7.0.5

1 finding

LOW No provenance attestation provenance

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

v7.0.4

1 finding

LOW No provenance attestation provenance

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

v7.0.3

1 finding

LOW No provenance attestation provenance

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

v7.0.2

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: parshap → goto-bus-stop (on 2018-02-28) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2018-02-28. This could indicate a legitimate maintainer transition or an account compromise.

v7.0.1

2 findings

HIGH Publisher changed: zertosh → parshap (on 2015-10-31) provenance

This version was published by a different npm account than previous versions on 2015-10-31. 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.

v7.0.0

2 findings

HIGH Publisher changed: parshap → zertosh (on 2015-10-26) provenance

This version was published by a different npm account than previous versions on 2015-10-26. 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.

v6.6.3

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: substack → parshap (on 2015-10-19) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-10-19. This could indicate a legitimate maintainer transition or an account compromise.

v6.6.2

1 finding

LOW No provenance attestation provenance

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

v6.6.1

1 finding

LOW No provenance attestation provenance

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

v6.6.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: zertosh → substack (on 2015-09-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-09-18. This could indicate a legitimate maintainer transition or an account compromise.

v6.5.2

1 finding

LOW No provenance attestation provenance

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

v6.5.1

1 finding

LOW No provenance attestation provenance

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

v6.5.0

1 finding

LOW No provenance attestation provenance

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

v6.4.3

1 finding

LOW No provenance attestation provenance

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

v6.4.2

1 finding

LOW No provenance attestation provenance

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

v6.4.1

1 finding

LOW No provenance attestation provenance

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

v6.4.0

1 finding

LOW No provenance attestation provenance

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

v6.3.0

2 findings

LOW No provenance attestation provenance

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

INFO Publisher changed: substack → zertosh (on 2015-04-26) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2015-04-26. This could indicate a legitimate maintainer transition or an account compromise.

v6.2.1

1 finding

LOW No provenance attestation provenance

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

v6.2.0

1 finding

LOW No provenance attestation provenance

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

v6.1.0

1 finding

LOW No provenance attestation provenance

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

v6.0.0

1 finding

LOW No provenance attestation provenance

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