@onerjs/core
Getting started? Play directly with the Babylon.js API using our [playground](https://playground.babylonjs.com/). It also contains a lot of samples to learn how to use it.
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): Package is a BabylonJS scoped distribution; name similarity to 'cors' is coincidental, not impersonation. | ai | |
| semgrep | semgrep:new-function-constructor | AI (semgrep): new Function() is in the Basis transcoder (BabylonJS asset), a well-known third-party WASM loader from the official BabylonJS repo. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 8.52.6 | 0 / 2 | |
| 8.52.5 | 0 / 2 | |
| 8.52.4 | 0 / 2 | |
| 8.52.2 | 0 / 2 | |
| 8.52.1 | 0 / 2 | |
| 8.51.9 | 0 / 2 | |
| 8.51.8 | 0 / 2 | |
| 8.51.7 | 0 / 2 | |
| 8.51.6 | 0 / 2 | |
| 8.51.5 | 0 / 2 | |
| 8.51.1 | 0 / 2 | |
| 8.50.9 | 0 / 2 |
v8.52.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.52.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.52.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.52.2
2 findingsPackage name '@onerjs/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.
v8.52.1
2 findingsPackage name '@onerjs/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.
v8.51.9
2 findingsPackage name '@onerjs/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.
v8.51.8
2 findingsPackage name '@onerjs/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.
v8.51.7
2 findingsPackage name '@onerjs/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.
v8.51.6
2 findingsPackage name '@onerjs/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.
v8.51.5
2 findingsPackage name '@onerjs/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.
v8.51.1
2 findingsPackage name '@onerjs/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.
v8.50.9
2 findingsPackage name '@onerjs/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.