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.

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

Private packages #40

Open
eridal opened this issue Nov 17, 2021 · 0 comments
Open

Private packages #40

eridal opened this issue Nov 17, 2021 · 0 comments

Comments

@eridal
Copy link
Contributor

eridal commented Nov 17, 2021

First, on October 26 we identified an issue caused by routine maintenance of one of our publicly available npm services. During maintenance on the database that powers the public npm replica at replicate.npmjs.com, records were created that could expose the names of private packages.

https://github.blog/2021-11-15-githubs-commitment-to-npm-ecosystem-security/#security-issues-related-to-the-npm-registry

So this package might be indexing private repos. It is sensible to..

  1. Audit the packages and remove the from the history.
  2. Introduce code to ensure that private repos are never added to the index
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant