Skip to content
This repository has been archived by the owner on Sep 29, 2021. It is now read-only.

NPM artifact signing for release #4

Open
maoo opened this issue Jul 28, 2016 · 1 comment
Open

NPM artifact signing for release #4

maoo opened this issue Jul 28, 2016 · 1 comment
Assignees
Labels
Milestone

Comments

@maoo
Copy link
Contributor

maoo commented Jul 28, 2016

To avoid tampering with NPM artifacts published (and maintained) by the Foundation, it is strongly recommended (if not mandatory, from a Foundation Security standpoint) to sign artifacts in order to prove their authenticity and avoid man-in-the-middle attacks.

The Java (Maven) release already includes such feature, which is widely endorsed by Maven Central (check https://symphonyoss.atlassian.net/wiki/display/FM/Software+Development+Onboarding#SoftwareDevelopmentOnboarding-MavenReleaseFeatures), but for NPM it's up to the project to enforce it, as it's not mandatory.

Looking for an NPM package that helps with the signing/deployment of GPG-signed artifacts.

@maoo maoo added this to the 1.0.0 milestone Jul 28, 2016
@maoo maoo self-assigned this Jul 28, 2016
@maoo
Copy link
Contributor Author

maoo commented Jul 29, 2016

After a long investigation I figured out that the NodeJS community is still trying to figure out how to implement npm package signing - node-forward/discussions#29

During my investigation I stumbled on https://s8f.org/salty.html , made by one of the guys involved in the discussion above; it looks like something definitely worth trying.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants