-
Notifications
You must be signed in to change notification settings - Fork 27
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
Clarify who did/can publish code for common packages #52
Comments
Hey, Currently, the dependencies are pulled from npm and pushed to soldeer central repository using npm, the crawler is run by me. using this code: https://github.com/mario-eth/soldeer-crawler I totally agree that one should not trust the soldeer maintainers to publish the right sources but until the projects are willing to do that I have to push them. |
https://github.com/mario-eth/soldeer?tab=readme-ov-file#dependencies-maintenance added readme docs. |
Thank you. The warning looks good to me ! |
https://soldeer.xyz/ mentions that it support, among other, @openzeppelin-contracts and @openzeppelin-contracts-upgradeable.
Has maintainers of this project, we are curious how our code is being retrieved when a user does:
That last option would be dangerous in our opinion. We want to ensure our users that they get code that was not tampered with, and that can be trusted.
Ideally they would only ahve to trust us. The current solution imply trusting either npmjs.com, or github, both of which are ok to most user (even though its not ideal). Trusting soldeer.xyz, or trusting a comunity maintainer that push code to soldeer.xyz, is very different IMO to trusting npm or github.
We'd like to understand the process more (and we think that should be very clearly documented on https://soldeer.xyz/project/@openzeppelin-contracts), so that we can inform our users accordingly.
The text was updated successfully, but these errors were encountered: