Nathan LaFreniere

@vroomcars my purchase has been in contracting since the 16th. What gives? I was told 24 hours

@Ilshidur sorry for the super late response (i rarely use twitter any more) but this is likely from me removing the github apps for nodesecurity's github integration when we shut down. that does show up kind of scary though, doesn't it?

@wraithgar it's ok, they're not in it for the fame, they're content quietly working in the background. they're really grinders.

@JimmyBrawn what's telling you 4.2.1 has problems? that release is patched, it was backported from 5.0.3. sounds like whatever is reporting your vulnerabilities needs to update their vuln definition

@quitlahok any idea what I can do about this? hoek 4.2.1 has known vulnerabilities: severity: low; summary: Prototype pollution attack; hackerone.com/reports/310439 babel 1.0.0 ↳ boom 4.3.1 ↳ hoek 4.2.1

@michaelbenin @nodesecurity sorry about that, little glitch on our end. if you hit the retry button it should pass now! if not send us an email support@nodesecurity.io

@arthaey @nodesecurity you can rename or delete your organization from the settings tab in the portal

@jongleberry @nodesecurity drop us a line at contact@nodesecurity.io if you need anything else, i can help more from there

@jongleberry @nodesecurity from your org view you should see a little red trash can top right of your integration's card, click that to remove it then you can re-add

Verifying myself: I am nlf on Keybase.io. 728tObbz_uva4SULz-CmHmId4CfmX-VTx3fj / keybase.io/nlf/sigs/728tO…

Join us in 5 min for a Node Security AMA @sideway sideway.com/room/d7

@nodesecurity @locn @eranhammer yeah, that was my fault. clearly bad timing for a deploy :)

@mattgrande @nodesecurity can you send us an email to contact@nodesecurity.io with some details so i can track down the issue?

@wraithgar @andyet violets are blue feathers are light charter let us know of that violated copyright

@HenrikJoreteg @nodesecurity and working on replacing the problem server

@HenrikJoreteg @nodesecurity yeah, our hosting provider is having problems again. we're working with them on getting it fixed

@HenrikJoreteg @nodesecurity all good now, sorry about that!

@HenrikJoreteg @nodesecurity checking it out right now

@HCornflower @LiftSecurity we do! for realsies

@wraithgar pretty sure you mean fedex office

@feross fyi i just fixed the nsp bug @adam_baldwin showed me you found