As a user of the Cacti npm packages I want to see on npmjs.com that the cacti packages are signed so that I have a layer of extra security against supply chain attacks that I can leverage.
Release process is still fully automated (which is a work in progress task at the time of this writing but nevertheless...)
Any changes to the release process should be documented
We have to retain the ability to issue releases by multiple maintainers (so signing keys shouldn't be generated/distributed in a way that there's any single point of failure)
Description
As a user of the Cacti npm packages I want to see on npmjs.com that the cacti packages are signed so that I have a layer of extra security against supply chain attacks that I can leverage.
https://github.blog/2023-04-19-introducing-npm-package-provenance/ https://blog.sigstore.dev/npm-public-beta/
Acceptance Criteria
--provenance
option so that the signature appears publicly on the registries ( for example https://www.npmjs.com/package/@hyperledger/cactus-cmd-api-server )