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

Doing this outside of NPM? #2

Open
goldingdamien opened this issue Nov 21, 2019 · 3 comments
Open

Doing this outside of NPM? #2

goldingdamien opened this issue Nov 21, 2019 · 3 comments

Comments

@goldingdamien
Copy link

I am thinking a security model that doesn't rely on package managers to take on the burden would be easier to push forwards. Would this be a possibility?

@wilk
Copy link
Owner

wilk commented Nov 21, 2019

I think it depends by the implementation.
The point is how transparent would be to the users.
Do you have any example?

@goldingdamien
Copy link
Author

No, I haven't really looked into it.
I was assuming a third party would perform the build and then create a checksum that can be checked against the file on npm. The third party could be either explicitly selected via a path or a list of trusted third parties could be centrally stored somewhere. This seems like something that would exist somewhere already(doesn't need to be npm specific), but I am not very familiar with this topic.

@wilk
Copy link
Owner

wilk commented Nov 27, 2019

@goldingdamien Yes, it could be possible.
Like a Certification Authority for HTTPS certificates or a trusted network of "build partners".
In fact, the huge problem SNPM has is about the resource for building the artifacts of so many projects.
It can be added to the workflow, of course 👍

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

2 participants