@metamask/create-release-branch
An interactive command-line tool to prepare a release branch by automatically bumping versions and updating changelogs for desired packages. Works for both polyrepos and monorepos.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/ui/assets/index-BUNXDfnY.js | AI (source-diff): Vite-bundled React UI output, not true obfuscation. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): express/open support the new local UI feature; validate-npm-package-name is a known utility. | ai | |
| source-diff | obfuscated-file:dist/ui/assets/index-DUbXgNZF.js | AI (source-diff): Vite-bundled React UI asset, not true obfuscation. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase is the new bundled UI, consistent with added build:ui script. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Normal maintainer roster churn at established MetaMask org. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 4.2.1 | 13 / 50 | |
| 4.2.0 | 13 / 50 | |
| 4.1.4 | 13 / 50 | |
| 4.1.3 | 13 / 49 | |
| 4.1.2 | 13 / 49 | |
| 4.1.1 | 13 / 49 | |
| 4.1.0 | 13 / 49 | |
| 4.0.0 | 10 / 38 |
v4.1.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.1.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.