@forge/bundler
Default bundler for Forge apps
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:tmp | AI (phantom-deps): Bundler tool; tmp used via config/runtime, not direct import. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:nock | AI (phantom-deps): Test utility referenced in config files; expected phantom pattern for this package. | ai | |
| phantom-deps | phantom-dep:ts-loader | AI (phantom-deps): Webpack loader referenced in config, not directly imported; stable for a bundler package. | ai | |
| phantom-deps | phantom-dep:type-fest | AI (phantom-deps): Type-only dependency; not directly imported at runtime. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:typescript | AI (phantom-deps): Invoked via CLI/config rather than direct import; expected for a bundler tool. | ai | |
| phantom-deps | phantom-dep:@babel/core | AI (phantom-deps): Framework-scoped, loaded by convention in webpack/babel config; stable for this bundler. | ai | |
| phantom-deps | phantom-dep:@babel/types | AI (phantom-deps): Babel types used transitively/by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:babel-loader | AI (phantom-deps): Webpack loader referenced in config files; stable phantom pattern for a bundler. | ai |
Versions (showing 29 of 29)
| Version | Deps | Published |
|---|---|---|
| 6.2.0 | 26 / 16 | |
| 6.1.26 | 26 / 16 | |
| 6.1.25 | 26 / 16 | |
| 6.1.24 | 26 / 16 | |
| 6.1.23 | 26 / 16 | |
| 6.1.22 | 26 / 16 | |
| 6.1.21 | 26 / 16 | |
| 6.1.20 | 26 / 16 | |
| 6.1.19 | 26 / 16 | |
| 6.1.18 | 26 / 16 | |
| 6.1.17 | 26 / 16 | |
| 6.1.16 | 26 / 16 | |
| 6.1.15 | 26 / 16 | |
| 6.1.14 | 26 / 16 | |
| 6.1.13 | 26 / 16 | |
| 6.1.12 | 26 / 16 | |
| 6.1.11 | 26 / 16 | |
| 6.1.10 | 26 / 16 | |
| 6.1.9 | 26 / 16 | |
| 6.1.8 | 26 / 16 | |
| 6.1.7 | 26 / 16 | |
| 6.1.6 | 26 / 16 | |
| 6.1.5 | 26 / 16 | |
| 6.1.4 | 26 / 16 | |
| 6.1.3 | 22 / 16 | |
| 6.1.2 | 22 / 16 | |
| 6.1.1 | 22 / 16 | |
| 6.1.0 | 23 / 16 | |
| 6.0.0 | 23 / 16 |
v6.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.