@babylonjs/core
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): @babylonjs/core is the canonical BabylonJS 3D engine, not a typosquat of 'cors'; scoped package name makes this a clear false positive. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is in Emscripten-generated basis_transcoder.js (WASM glue code); standard pattern, not a security concern for this package. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 9.10.1 | 0 / 2 | |
| 9.10.0 | 0 / 2 | |
| 9.9.2 | 0 / 2 | |
| 9.9.1 | 0 / 2 | |
| 9.9.0 | 0 / 2 | |
| 9.8.0 | 0 / 2 | |
| 9.7.0 | 0 / 2 | |
| 9.5.1 | 0 / 2 | |
| 9.5.0 | 0 / 2 | |
| 9.4.1 | 0 / 2 |
v9.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.4.1
2 findingsPackage name '@babylonjs/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.