To my eyes it does line up correctly,  I frequently write things like

```js
var output = input
  .filter(function (v) {
    return v.propA
  })
  .map(function (v) {
    return v.propB
  })
// or
input
  .filter(function (v) {
    return v.propA
  })
  .map(function (v) {
    return v.propB
  })
  .forEach(function (v) {
    v.execute()
  })
```

In this case `function (v) { v.execute() }` isn't the top level, The top level is a Call Expression which calls `.forEach` on the input that's been filtered and mapped.  As such it is correct for the function to be indented an extra level.

Even if I were writing:

```js
input.forEach(function (v) {
  v.execute()
})
```

it would not be totally unreasonable to write:

```js
input.forEach(function (v) {
    v.execute()
  })
```

although that looks odd for such a small function, it can make sense on larger functions.

In any case, this is all just bike shedding, ultimately these kinds of style points are largely arbitrary and that's why GitHub repositories all have one person who gets to just make the final decision.  It makes no practical difference and will in no way prevent you using this library to the fullest extent possible, so it's not really up for debate.