webpack-stats-plugin — Greenflagged

Webpack stats plugin

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

scottianstewartkeithluchtelcecepparobwalkercogksandersarahformidablescott-rippeyyankovaleramichaelmerrillsarmeyermariano-formidablecarlospaelinckryan.roemerformidable-ownereastridgeexogenjmcbee1formidablelabscarbonrobotmasiddee

Keywords

webpack

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
provenance	no-provenance	AI (provenance): Established package predating provenance support; publisher is long-trusted. Stable FP for this package.	ai	2026/04/24
provenance	publisher-changed	AI (provenance): Publisher moved from personal account (ryan.roemer) to org account (formidablelabs) — both belong to Formidable Labs, consistent with repo URL and author field.	ai	2026/04/24
maintainer-change	maintainer-added	AI (maintainer-change): New maintainers are Formidable Labs team members; normal org team rotation.	ai	2026/04/24
maintainer-change	maintainer-removed	AI (maintainer-change): Removed maintainers are former Formidable Labs team members; normal org team rotation.	ai	2026/04/24

Versions (showing 23 of 23)

Version	Deps	Published
1.1.3	0 / 20	2023-06-02
1.1.2	0 / 20	2023-06-02
1.1.1	0 / 18	2022-10-29
1.1.0	0 / 18	2022-08-12
1.0.3	0 / 17	2020-12-25
1.0.2	0 / 17	2020-10-29
1.0.1	0 / 17	2020-10-20
1.0.0	0 / 17	2020-10-15
0.3.2	0 / 14	2020-06-17
0.3.1	0 / 14	2019-12-18
0.3.0	0 / 14	2019-07-10
0.2.1	0 / 14	2018-03-01
0.2.0	0 / 7	2018-02-28
0.1.5	0 / 5	2017-03-31
0.1.4	0 / 5	2016-10-29
0.1.3	0 / 5	2016-07-05
0.1.2	0 / 5	2016-07-05
0.1.1	0 / 5	2015-09-30
0.1.0	0 / 5	2015-07-16
0.0.4	0 / 5	2015-02-28
0.0.3	0 / 4	2015-02-09
0.0.2	0 / 4	2015-02-08
0.0.1	0 / 4	2015-02-08

v1.1.3

1 finding

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v0.2). This is the strongest supply chain integrity signal.

v1.1.2

2 findings

HIGH Publisher changed: ryan.roemer → formidablelabs (on 2023-06-02) provenance

This version was published by a different npm account than previous versions on 2023-06-02. 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.

v1.1.1

1 finding

LOW No provenance attestation provenance

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

v1.1.0

1 finding

LOW No provenance attestation provenance

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

v1.0.3

1 finding

LOW No provenance attestation provenance

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

v1.0.2

1 finding

LOW No provenance attestation provenance

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

v1.0.1

1 finding

LOW No provenance attestation provenance

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

v1.0.0

1 finding

LOW No provenance attestation provenance

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

v0.3.2

1 finding

LOW No provenance attestation provenance

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

v0.3.1

1 finding

INFO No provenance attestation provenance

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

v0.3.0

2 findings

HIGH Unclaimed maintainer email domain: michaelmerrill.io email-domain

Maintainer email '[email protected]' uses domain 'michaelmerrill.io' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.

LOW No provenance attestation provenance

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

v0.2.1

1 finding

LOW No provenance attestation provenance

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

v0.2.0

1 finding

LOW No provenance attestation provenance

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

v0.1.5

1 finding

INFO No provenance attestation provenance

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

v0.1.4

1 finding

INFO No provenance attestation provenance

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

v0.1.3

1 finding

INFO No provenance attestation provenance

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

v0.1.2

1 finding

INFO No provenance attestation provenance

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

v0.1.1

1 finding

INFO No provenance attestation provenance

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

v0.1.0

1 finding

INFO No provenance attestation provenance

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

v0.0.4

1 finding

LOW No provenance attestation provenance

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

v0.0.3

1 finding

INFO No provenance attestation provenance

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

v0.0.2

1 finding

INFO No provenance attestation provenance

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

v0.0.1

1 finding

INFO No provenance attestation provenance

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