feat(security): Add provenance (#339)

* Enable provenance in package.json

* Add necessary permissions to the release workflow

* Add provenance to project init

* style: prettier

---------

Co-authored-by: wolfy1339 <[email protected]>

Author: AaronDewes

.github/workflows/release.yml

@@ -3,6 +3,13 @@ name: Release
   push:
     branches:
       - main
+# These are recommended by the semantic-release docs: https://github.com/semantic-release/npm#npm-provenance
+permissions:
+    contents: write # to be able to publish a GitHub release
+    issues: write # to be able to comment on released issues
+    pull-requests: write # to be able to comment on released pull requests
+    id-token: write # to enable use of OIDC for npm provenance
+
 jobs:
   release:
     name: release

lib/create-package-json.js

@@ -71,6 +71,7 @@ async function createPackageJson(answers) {
   if (answers.publicAccess) {
     pkg.publishConfig = {
       access: "public",
+      provenance: true,
     };
   }
 

lib/create-release-action.js

@@ -15,6 +15,12 @@ on:
       - next
       - beta
       - "*.x" # maintenance release branches, e.g. v1.x
+# These are recommended by the semantic-release docs: https://github.com/semantic-release/npm#npm-provenance
+permissions:
+    contents: write # to be able to publish a GitHub release
+    issues: write # to be able to comment on released issues
+    pull-requests: write # to be able to comment on released pull requests
+    id-token: write # to enable use of OIDC for npm provenance
 
 jobs:
   release:

package.json

@@ -36,5 +36,8 @@
   },
   "engines": {
     "node": ">= 18"
+  },
+  "publishConfig": {
+    "provenance": true
   }
 }