@genesislcap/foundation-shell
Genesis Foundation Shell
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/main.d02320089aa26d048dcb.js | AI (source-diff): Standard webpack bundle with CSS-in-JS; minification is expected for this build pipeline. | ai | |
| source-diff | obfuscated-file:dist/main.0e8ca22628a117f16a5f.js | AI (source-diff): Standard webpack bundle output for this Genesis shell package; not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:dist/npm.consola.00ba577c5cd42994a359.js | AI (source-diff): Minified consola logger bundle; recognizable library code, no malicious patterns. | ai | |
| source-diff | obfuscated-file:dist/npm.microsoft.9b7cca951db576bc267c.js | AI (source-diff): Minified Microsoft FAST component bundle; standard webpack output for this package. | ai |
Versions (showing 51 of 349)
| Version | Deps | Published |
|---|---|---|
| 14.449.0 | 11 / 7 | |
| 14.448.0 | 11 / 7 | |
| 14.447.2 | 11 / 7 | |
| 14.447.1 | 11 / 7 | |
| 14.447.0 | 11 / 7 | |
| 14.446.2 | 11 / 7 | |
| 14.446.1 | 11 / 7 | |
| 14.446.0 | 11 / 7 | |
| 14.445.2 | 11 / 7 | |
| 14.445.1 | 11 / 7 | |
| 14.445.0 | 11 / 7 | |
| 14.444.1 | 11 / 7 | |
| 14.444.0 | 11 / 7 | |
| 14.443.1 | 11 / 7 | |
| 14.443.0 | 11 / 7 | |
| 14.442.0 | 11 / 7 | |
| 14.441.0 | 11 / 7 | |
| 14.439.3 | 11 / 7 | |
| 14.439.2 | 11 / 7 | |
| 14.439.1 | 11 / 7 | |
| 14.439.0 | 11 / 7 | |
| 14.438.1 | 11 / 7 | |
| 14.438.0 | 11 / 7 | |
| 14.437.6 | 11 / 7 | |
| 14.437.5 | 11 / 7 | |
| 14.437.4 | 11 / 7 | |
| 14.437.3 | 11 / 7 | |
| 14.437.2 | 11 / 7 | |
| 14.437.1 | 11 / 7 | |
| 14.437.0 | 11 / 7 | |
| 14.436.0 | 11 / 7 | |
| 14.435.0 | 11 / 7 | |
| 14.434.0 | 11 / 7 | |
| 14.433.1 | 11 / 7 | |
| 14.433.0 | 11 / 7 | |
| 14.432.2 | 11 / 7 | |
| 14.432.1 | 11 / 7 | |
| 14.432.0 | 11 / 7 | |
| 14.431.0 | 11 / 7 | |
| 14.430.2 | 11 / 7 | |
| 14.430.1 | 11 / 7 | |
| 14.430.0 | 11 / 7 | |
| 14.429.3 | 11 / 7 | |
| 14.429.2 | 11 / 7 | |
| 14.429.1 | 11 / 7 | |
| 14.429.0 | 11 / 7 | |
| 14.428.1 | 11 / 7 | |
| 14.428.0 | 11 / 7 | |
| 14.427.1 | 11 / 7 | |
| 14.427.0 | 11 / 7 | |
| 14.426.0 | 11 / 7 |
v14.449.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.448.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.447.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.447.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.447.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.446.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.446.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.446.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.445.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.445.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.445.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.444.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.444.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.
v14.443.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.
v14.443.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.
v14.442.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.
v14.441.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.439.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.439.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.439.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.439.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.438.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.438.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.437.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.437.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.437.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.437.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.437.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.437.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.437.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.436.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.435.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.434.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.433.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.433.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.432.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.432.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.432.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.431.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.430.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.430.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.430.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.429.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.429.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.429.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.429.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.428.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.428.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.427.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.427.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.426.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.