-
The crossref middleware checks the DOI pattern to crossref from firing an error. DOIs with a bad pattern should be available somewhere.
-
## CVE-2022-24999 - High Severity Vulnerability
Vulnerable Libraries - qs-6.7.0.tgz, qs-6.2.3.tgz, qs-6.5.2.tgz, qs-6.9.0.tgz
qs-6.7.0.tgz
A querystring parser that supports nesting and arrays, wi…
-
Right now qs (and thus connect's bodyParser) cannot handle formdata that would be illegal utf8 (i.e. %DF) and return an error. A prominent Example would be paypal's ipn messages, which use a windows-1…
-
## CVE-2022-24999 - High Severity Vulnerability
Vulnerable Libraries - qs-6.5.2.tgz, qs-6.7.0.tgz
qs-6.5.2.tgz
A querystring parser that supports nesting and arrays, with a depth limit
Library hom…
-
- **I'm submitting a ...**
- [x] feature request
- **Summary**
I wish it works like this:
```ts
contractsGetBigMapByNameKeys(
address,
'name',
{
value: {
toke…
-
node-sqlparser _does_ parse `FREETEXT(foo, 'bar')` but it does _not_ parse `FREETEXT(*, 'bar')` (with the wildcard)
(ref timwis/node-soda2-parser#1)
-
Issue created as a result of [this Posit Community thread](https://community.rstudio.com/t/plumber-param-collision-in-dynamic-path-and-query-string/173658).
In spinning-up an API, I realized I had …
-
```haxe
@:params(bar('bar-$_') in query)
function get(bar:DynamicAccess);
```
and a request with `?bar-foo=a&bar-baz=b` would be translated to `{foo:'a', baz:'b'}` in Haxe.
Any thoughts?
-
## CVE-2021-44907 - Low Severity Vulnerability
Vulnerable Libraries - qs-6.5.2.tgz, qs-0.6.6.tgz, qs-6.10.1.tgz, qs-6.7.0.tgz
qs-6.5.2.tgz
A querystring parser that supports nesting and arrays, wi…
-
## CVE-2021-44907 - Low Severity Vulnerability
Vulnerable Libraries - qs-6.5.2.tgz, qs-0.6.6.tgz, qs-6.7.0.tgz, qs-6.10.1.tgz
qs-6.5.2.tgz
A querystring parser that supports nesting and arrays, wi…