babylonjs
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): BabylonJS is a major established 3D engine; long gap likely reflects npm publishing strategy change, not takeover. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Long-standing postinstall pattern for the official BabylonJS package; stable across versions. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 9.9.0 | 0 / 2 | |
| 9.8.0 | 0 / 2 | |
| 9.7.0 | 0 / 2 | |
| 9.6.2 | 0 / 2 | |
| 9.5.0 | 0 / 2 | |
| 9.4.1 | 0 / 7 | |
| 9.2.1 | 0 / 7 |
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.6.2
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.