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

Investigate more robust dependency management for high-impact dependencies #458

Open
mgwalker opened this issue Sep 22, 2022 · 0 comments
Open

Comments

@mgwalker
Copy link
Member

In particular, the @slack/bolt dependency does a huge amount of our security legwork. Is there more we can do to verify that we have the genuine article from NPM, and not something that has been compromised?

One possibility might be cloning the Bolt repo and pulling into Charlie from that. Then we could update Bolt periodically from upstream, but since we'd be taking NPM out of the equation, we wouldn't have that to worry about.

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