browserslist-useragent
A utility to match a browselist query to browser user agents
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Established package with trusted publisher track record; missing gitHead reflects a publish environment change but no other risk signals are present. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance; absence of attestation is expected for this maintainer's workflow and not a risk indicator given clean history. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): ua-parser-js is a well-known UA parsing library and a natural replacement for the removed 'useragent' dep in this UA-matching utility. Not a suspicious injection. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 4.0.0 | 2 / 13 | |
| 3.1.4 | 5 / 6 | |
| 3.1.3 | 4 / 6 | |
| 3.1.2 | 4 / 6 | |
| 3.1.1 | 4 / 6 | |
| 3.1.0 | 3 / 6 | |
| 3.0.3 | 3 / 5 | |
| 3.0.2 | 3 / 5 | |
| 3.0.1 | 3 / 5 | |
| 3.0.0 | 3 / 5 | |
| 2.0.1 | 3 / 5 | |
| 2.0.0 | 3 / 5 | |
| 1.2.1 | 3 / 5 | |
| 1.2.0 | 3 / 5 | |
| 1.1.0 | 3 / 5 | |
| 1.0.5 | 3 / 5 | |
| 1.0.4 | 3 / 5 | |
| 1.0.3 | 3 / 5 | |
| 1.0.2 | 3 / 5 | |
| 1.0.1 | 3 / 5 | |
| 1.0.0 | 3 / 5 | |
| 0.0.2 | 3 / 1 | |
| 0.0.1 | 3 / 1 |
v4.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pastelsky.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pastelsky.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: pastelsky.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.