-
Notifications
You must be signed in to change notification settings - Fork 195
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
security-check fails #24
Comments
nsp was acquired by npm, so it's now built into npm. You no longer need to manually run nsp. Check out this PR for updates on how to run the latest versions. |
thx :) i would suggest either editing the course (which is great) or sticking up one of those blue post it notes |
What in the hell is going on?
What part of my background is off?
I worked at the Jet Propulsion Laboratory for 25 years. I have held a
military security clearance for most of my life. I WAS happily subscribed
for months.
I will forward this mess to Cory.
…On Wed, Dec 12, 2018, 2:11 PM gregor ***@***.*** wrote:
nsp check
(+) Client request error: getaddrinfo ENOTFOUND api.nodesecurity.io
api.nodesecurity.io:443
(running nsp check here on it's own just to show the error)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#24>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ACfSKq3C-O82x45xWwxW1Dh_fRtWligUks5u4VTIgaJpZM4ZQRLR>
.
|
I've already added a blue note to the relevant clips in the course. That note was added months ago. Did you guys just overlook it? @Chris-43 - What is your issue? |
I see what happened - yes you are right there is a blue note in the package management section but one is missing in the Automation - Demo: Create Security Check and Share Scripts. [only checking cos I love you ;) ] |
@gbm - Ah! Great catch! I just submitted a patch to add a callout on that clip, and the following clip as well since it shows calling the security-check clip. Thanks! 💯 |
nsp check
(+) Client request error: getaddrinfo ENOTFOUND api.nodesecurity.io api.nodesecurity.io:443
(running nsp check here on it's own just to show the error)
The text was updated successfully, but these errors were encountered: