browserslist-generator
A library that makes generating and validating Browserslists a breeze!
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Trusted publisher (wessberg, 273 approved/0 rejected) changed build tooling to tsup in v3.0.0; missing gitHead is consistent with a legitimate CI/build environment change, not a supply chain compromise. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): [email protected] is an established, legitimate bot-detection library; new dep addition is benign for this package. | ai | |
| dependencies | unvetted-dep:@types/semver | AI (dependencies): Official TypeScript type definitions for semver; no security concern. | ai | |
| dependencies | unvetted-dep:isbot | AI (dependencies): isbot is a legitimate, well-known bot detection library; appropriate dependency for a browserslist utility. | ai | |
| dependencies | unvetted-dep:@types/object-path | AI (dependencies): Official TypeScript type definitions for object-path; no security concern. | ai | |
| dependencies | unvetted-dep:@types/ua-parser-js | AI (dependencies): Official TypeScript type definitions for ua-parser-js; no security concern. | ai | |
| dependencies | unvetted-dep:@mdn/browser-compat-data | AI (dependencies): MDN's official browser compatibility data package; core dependency for a browserslist utility. | ai | |
| provenance | no-provenance | AI (provenance): Provenance attestation is a nice-to-have; absence does not indicate security risk for this established package. | ai | |
| dependencies | unvetted-dep:ua-parser-js | AI (dependencies): ua-parser-js is a widely-used, established user-agent parser; unvetted status does not indicate risk here. | ai | |
| phantom-deps | phantom-dep:@types/ua-parser-js | AI (phantom-deps): TypeScript type definitions are framework-scoped and loaded by convention; standard for typed packages. | ai | |
| phantom-deps | phantom-dep:@types/semver | AI (phantom-deps): TypeScript type definitions are framework-scoped and loaded by convention; standard for typed packages. | ai | |
| phantom-deps | phantom-dep:@types/object-path | AI (phantom-deps): TypeScript type definitions are framework-scoped and loaded by convention; standard for typed packages. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 3.0.0 | 10 / 25 | |
| 2.3.0 | 10 / 27 | |
| 2.2.0 | 10 / 27 | |
| 2.1.0 | 10 / 27 | |
| 2.0.3 | 10 / 26 | |
| 2.0.2 | 10 / 26 | |
| 2.0.1 | 10 / 25 | |
| 1.0.66 | 10 / 23 | |
| 1.0.65 | 10 / 23 | |
| 1.0.64 | 10 / 23 | |
| 1.0.63 | 10 / 23 | |
| 1.0.62 | 10 / 23 | |
| 1.0.61 | 10 / 23 | |
| 1.0.60 | 10 / 23 | |
| 1.0.59 | 10 / 23 | |
| 1.0.58 | 10 / 23 | |
| 1.0.57 | 10 / 23 | |
| 1.0.56 | 10 / 23 | |
| 1.0.55 | 10 / 23 | |
| 1.0.54 | 10 / 23 | |
| 1.0.53 | 10 / 23 | |
| 1.0.52 | 10 / 23 | |
| 1.0.51 | 10 / 23 | |
| 1.0.50 | 10 / 23 | |
| 1.0.49 | 9 / 23 | |
| 1.0.48 | 9 / 23 |
v2.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.66
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.65
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.60
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.54
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.