@tinkoff/user-agent
A set of methods for parsing userAgent and getting browser data. Library for parsing and executing checks by:
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a known implicit TypeScript runtime dep; stable false positive for this package. | ai |
Versions (showing 100 of 889)
| Version | Deps | Published |
|---|---|---|
| 0.8.160 | 5 / 2 | |
| 0.8.159 | 5 / 2 | |
| 0.8.158 | 5 / 2 | |
| 0.8.157 | 5 / 2 | |
| 0.8.156 | 5 / 2 | |
| 0.8.155 | 5 / 2 | |
| 0.8.153 | 5 / 2 | |
| 0.8.152 | 5 / 2 | |
| 0.8.124 | 5 / 2 | |
| 0.8.122 | 5 / 2 | |
| 0.8.121 | 5 / 2 | |
| 0.8.120 | 5 / 2 | |
| 0.8.119 | 5 / 2 | |
| 0.8.118 | 5 / 2 | |
| 0.8.117 | 5 / 2 | |
| 0.8.116 | 5 / 2 | |
| 0.8.112 | 5 / 2 | |
| 0.8.110 | 5 / 2 | |
| 0.8.109 | 5 / 2 | |
| 0.8.107 | 5 / 2 | |
| 0.8.106 | 5 / 2 | |
| 0.8.105 | 5 / 2 | |
| 0.8.102 | 5 / 2 | |
| 0.7.292 | 5 / 2 | |
| 0.7.289 | 5 / 2 | |
| 0.7.288 | 5 / 2 | |
| 0.7.287 | 5 / 2 | |
| 0.7.283 | 5 / 2 | |
| 0.7.280 | 5 / 2 | |
| 0.7.279 | 5 / 2 | |
| 0.7.274 | 5 / 2 | |
| 0.7.270 | 5 / 2 | |
| 0.7.268 | 5 / 2 | |
| 0.7.267 | 5 / 2 | |
| 0.7.266 | 5 / 2 | |
| 0.7.264 | 5 / 2 | |
| 0.7.247 | 5 / 2 | |
| 0.7.246 | 5 / 2 | |
| 0.7.244 | 5 / 2 | |
| 0.7.242 | 5 / 2 | |
| 0.7.241 | 5 / 2 | |
| 0.7.240 | 5 / 2 | |
| 0.7.239 | 5 / 2 | |
| 0.7.238 | 5 / 2 | |
| 0.7.236 | 5 / 2 | |
| 0.7.235 | 5 / 2 | |
| 0.7.218 | 5 / 2 | |
| 0.7.205 | 5 / 2 | |
| 0.7.204 | 5 / 2 | |
| 0.7.203 | 5 / 2 | |
| 0.7.202 | 5 / 2 | |
| 0.7.198 | 5 / 2 | |
| 0.7.116 | 5 / 2 | |
| 0.7.115 | 5 / 2 | |
| 0.7.113 | 5 / 2 | |
| 0.7.112 | 5 / 2 | |
| 0.7.111 | 5 / 2 | |
| 0.7.110 | 5 / 2 | |
| 0.7.108 | 5 / 2 | |
| 0.7.106 | 5 / 2 | |
| 0.7.99 | 5 / 2 | |
| 0.7.98 | 5 / 2 | |
| 0.7.96 | 5 / 2 | |
| 0.7.67 | 5 / 2 | |
| 0.7.65 | 5 / 2 | |
| 0.7.64 | 5 / 2 | |
| 0.7.62 | 5 / 2 | |
| 0.7.61 | 5 / 2 | |
| 0.7.60 | 5 / 2 | |
| 0.7.58 | 5 / 2 | |
| 0.7.55 | 5 / 2 | |
| 0.7.54 | 5 / 2 | |
| 0.7.52 | 5 / 2 | |
| 0.7.51 | 5 / 2 | |
| 0.7.50 | 5 / 2 | |
| 0.7.49 | 5 / 2 | |
| 0.7.47 | 5 / 2 | |
| 0.7.46 | 5 / 2 | |
| 0.7.27 | 5 / 2 | |
| 0.7.26 | 5 / 2 | |
| 0.7.25 | 5 / 2 | |
| 0.7.23 | 5 / 2 | |
| 0.7.21 | 5 / 2 | |
| 0.7.19 | 5 / 2 | |
| 0.7.17 | 5 / 2 | |
| 0.7.16 | 5 / 2 | |
| 0.7.14 | 5 / 2 | |
| 0.7.13 | 5 / 2 | |
| 0.7.11 | 5 / 2 | |
| 0.7.10 | 5 / 2 | |
| 0.7.8 | 5 / 2 | |
| 0.7.5 | 5 / 2 | |
| 0.7.4 | 5 / 2 | |
| 0.7.3 | 5 / 2 | |
| 0.7.2 | 5 / 2 | |
| 0.6.259 | 5 / 2 | |
| 0.6.258 | 5 / 2 | |
| 0.6.251 | 5 / 2 | |
| 0.6.246 | 5 / 2 | |
| 0.6.245 | 5 / 2 |
v0.7.292
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.289
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.288
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.287
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.116
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.113
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.67
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.64
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.55
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.54
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.50
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.49
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.47
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.46
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.21
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.17
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.