Hacker GitHub

← All repos

node-forward/discussions

View on GitHub ↗ ★ 148

Soliciting ideas and feedback for community driven collaborative projects that help Node.

16 mentions on Hacker News by 14 people: 1 story, 15 comments · first 2014-10-16 · latest 2026-04-23

Mentions per year 16 mentions · busiest year 2014 (4)
20082026
  1. …to implement security features that would have made attacks like this harder really doesn't help https://github.com/node-forward/discussions/issues/29
  2. …https://docs.ruby-lang.org/en/master/Gem/Security.html [3] https://github.com/npm/npm/pull/4016 [4] https://github.com/node-forward/discussions/issues/29
  3. …with something better than PGP. Still waiting 10 years later. https://github.com/npm/npm/pull/4016 https://github.com/node-forward/discussions/issues/29#issuec... Meanwhile PGP secures the supply chain of the Linux distros that power the…
    comment by lrvick · 2023-12-14 · in Ledger's NPM account has been hacked
  4. …same reason -- they'd convey a false expectation without a solution for key verification.[2] [1] https://github.com/node-forward/discussions/issues/29 [2] https://github.com/Homebrew/brew/pull/4120#issuecomment-4068...
  5. …a more granular, per-module approach to this during the Node Forward and IO.js debacle years ago: https://github.com/node-forward/discussions/issues/14 At the time it was deemed to difficult to implement in Node.js after the fact, which…
  6. …service to it and dodge the problem than it is to add any friction to their potential growth. [1] https://github.com/node-forward/discussions/issues/29
    comment by micaksica · 2018-01-08 · in Npm operational incident, 6 Jan 2018
  7. …://news.ycombinator.com/item?id=14905870 Literally nothing was done for 158 days. You yourself asked: https://github.com/node-forward/discussions/issues/29#issuec... "How would package signing prevent people from requesting the wrong…
    comment by danjoc · 2018-01-06 · in Many packages suddenly disappeared
  8. maybe it's time to push for adding signed packages to npm long discussion here: https://github.com/node-forward/discussions/issues/29
    comment by no29 · 2018-01-06 · in Many packages suddenly disappeared
  9. …to "better solutions" that don't exist and will never exist. They've done literally nothing. https://github.com/node-forward/discussions/issues/29 Last discussion was > 1 year ago. They simply do not care. Security isn't even an…
    comment by danjoc · 2017-08-01 · in Malicious crossenv package on npm
  10. …required to just understand what might be vulnerable. [1] https://docs.npmjs.com/misc/scripts [2] https://github.com/node-forward/discussions/issues/29 [3] https://github.com/ChALkeR/notes/blob/master/Do-not-underest... [4]…
  11. This is one of the most important points. And an issue for it has been open since Jan 2015: https://github.com/node-forward/discussions/issues/29 It's, imo, negligent.
    comment by mikegerwitz · 2016-08-03 · in React Native for Ubuntu
  12. ▲ 1
    All the Maths (2014)
    story by tosh · 2015-05-14 · 0 comments
  13. …be easy, they are ancient and I am async!" ... "I failed to compile these ancient libraries." https://github.com/node-forward/discussions/issues/1
    comment by scljstcwombat · 2014-11-28 · in IO.js – Evented I/O for V8 javascript
  14. …to get their stuff merged back into node mainline. The GitHub fork has since been made private ( https://github.com/node-forward/discussions/issues/7 ) and they're working to set up a proper governance model so that the community can truly…
  15. …as zzmp pointed out, there is a fair bit of discussion around indicating some political discontent: https://github.com/node-forward/discussions/issues/7
    comment by lucideer · 2014-10-16 · in Why Is Node Being Forked?
  16. …in their issues [1] that it's just politics. They've taken it private for the time being. [1] https://github.com/node-forward/discussions/issues/7
    comment by zzmp · 2014-10-16 · in Why Is Node Being Forked?