@saltcorn/mobile-builder
plugin to to build a mobile app from a tenant application
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Webpack config uses require.resolve to locate sibling monorepo packages; stable pattern across all versions. | ai | |
| phantom-deps | phantom-dep:webpack | AI (phantom-deps): webpack is declared in dependencies and used via webpack.config.js; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:webpack-cli | AI (phantom-deps): webpack-cli is declared in dependencies and invoked via build script; phantom-dep heuristic false positive. | ai | |
| phantom-deps | phantom-dep:@saltcorn/db-common | AI (phantom-deps): Same-org sibling package; used transitively within the monorepo. Stable false positive. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.5.7 | 14 / 6 | |
| 1.5.6 | 14 / 6 | |
| 1.5.5 | 14 / 6 | |
| 1.5.4 | 14 / 6 | |
| 1.5.3 | 14 / 6 | |
| 1.5.2 | 14 / 6 | |
| 1.5.0 | 14 / 6 | |
| 1.4.6 | 14 / 5 | |
| 1.4.5 | 14 / 5 | |
| 1.4.4 | 14 / 5 | |
| 1.4.3 | 14 / 5 | |
| 1.4.2 | 14 / 5 | |
| 1.4.1 | 14 / 5 | |
| 1.4.0 | 14 / 5 | |
| 1.3.1 | 14 / 5 | |
| 1.3.0 | 14 / 5 | |
| 1.2.0 | 14 / 5 |
v1.5.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.