@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.a86036ac3429d14a431b.js | AI (source-diff): Standard webpack bundle output for this Genesis shell package; consistent with prior versions. | ai | |
| source-diff | obfuscated-file:dist/main.c856f0e207ca039b1020.js | AI (source-diff): Standard webpack bundle output for this Genesis shell package; consistent with prior versions. | ai | |
| source-diff | obfuscated-file:dist/npm.microsoft.4c8d41dd0aa1785e09d5.js | AI (source-diff): Standard webpack bundle (FAST/Microsoft web components); consistent with this package's known dependencies. | ai | |
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo CI pipeline publishes all packages simultaneously; rapid publish is expected for this org. | ai | |
| 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 49 of 380)
| Version | Deps | Published |
|---|---|---|
| 14.284.3 | 11 / 8 | |
| 14.284.2 | 11 / 8 | |
| 14.284.1 | 11 / 8 | |
| 14.284.0 | 11 / 8 | |
| 14.283.2 | 11 / 8 | |
| 14.283.1 | 11 / 8 | |
| 14.283.0 | 11 / 8 | |
| 14.282.0 | 11 / 8 | |
| 14.281.2 | 11 / 8 | |
| 14.281.1 | 11 / 8 | |
| 14.281.0 | 11 / 8 | |
| 14.280.0 | 11 / 8 | |
| 14.278.3 | 11 / 8 | |
| 14.278.2 | 11 / 8 | |
| 14.278.1 | 11 / 8 | |
| 14.278.0 | 11 / 8 | |
| 14.277.0 | 11 / 8 | |
| 14.276.3 | 11 / 8 | |
| 14.276.2 | 11 / 8 | |
| 14.276.1 | 11 / 8 | |
| 14.276.0 | 11 / 8 | |
| 14.275.3 | 11 / 8 | |
| 14.275.2 | 11 / 8 | |
| 14.275.1 | 11 / 8 | |
| 14.275.0 | 11 / 8 | |
| 14.274.1 | 11 / 8 | |
| 14.274.0 | 11 / 8 | |
| 14.273.0 | 11 / 8 | |
| 14.272.0 | 11 / 8 | |
| 14.271.2 | 11 / 8 | |
| 14.271.1 | 11 / 8 | |
| 14.271.0 | 11 / 8 | |
| 14.270.0 | 11 / 8 | |
| 14.269.0 | 11 / 8 | |
| 14.268.4 | 11 / 8 | |
| 14.268.3 | 11 / 8 | |
| 14.268.2 | 11 / 8 | |
| 14.268.1 | 11 / 8 | |
| 14.268.0 | 11 / 8 | |
| 14.267.0 | 11 / 8 | |
| 14.266.1 | 11 / 8 | |
| 14.266.0 | 11 / 8 | |
| 14.265.1 | 11 / 8 | |
| 14.265.0 | 11 / 8 | |
| 14.264.4 | 11 / 8 | |
| 14.264.3 | 11 / 8 | |
| 14.264.2 | 11 / 8 | |
| 14.264.1 | 11 / 8 | |
| 14.264.0 | 11 / 8 |
v14.284.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.284.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.284.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.284.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.283.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.283.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.283.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.282.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.281.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.281.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.281.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.280.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.278.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.278.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.278.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.278.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.277.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.276.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.276.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.276.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.276.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.275.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.275.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.275.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.275.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.274.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.274.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.273.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.272.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.271.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.271.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.271.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.270.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.269.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.268.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.268.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.268.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.268.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.268.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.267.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.266.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.266.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.265.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.265.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.264.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.264.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.264.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.264.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v14.264.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.