Skip to content
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.

Sign up for GitHub

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

Jump to bottom

cover security #99

Open
aladdin-add opened this issue Mar 13, 2019 · 3 comments
Open

cover security #99

aladdin-add opened this issue Mar 13, 2019 · 3 comments

Comments

@aladdin-add
Copy link

some thoughts(but it should be more):

  • it is recommended to enable 2fa.
  • npm audit
@sapegin
Copy link
Member

sapegin commented Mar 14, 2019

I've just added a few bits on npm audit in #97. Would you add anything else?

Do you mean 2FA on npm, GitHub or 2FA in general?

@aladdin-add
Copy link
Author

Do you mean 2FA on npm, GitHub or 2FA in general?

2FA in general, but npm seems to be more important.(since its have more downloads).
The idea is initially inspired by https://eslint.org/blog/2018/07/postmortem-for-malicious-package-publishes

@sapegin
Copy link
Member

sapegin commented Mar 14, 2019

Yeah, that's a tricky thing because it doesn't work with tools like semantic-release. Worth mentioning that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@sapegin @aladdin-add