@xiping/babylon-store
轻量 Babylon.js 场景封装，提供常用的相机控制、模型/高斯 splat 加载、辅助几何和视图导航能力。
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 |
|---|---|---|---|---|
| npm-metadata | no-description | AI (npm-metadata): Established scoped package with 35 versions; missing description is low-risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Legitimate library wrapper; metadata gaps are common in specialized packages. | ai | |
| dependencies | unvetted-dep:babylon-viewport-gizmo | AI (dependencies): BabylonJS ecosystem utility; consistent with package purpose. | ai | |
| dependencies | unvetted-dep:@babylonjs/havok | AI (dependencies): Official BabylonJS physics plugin; stable false positive for this package. | ai | |
| dependencies | unvetted-dep:@babylonjs/gui | AI (dependencies): Well-known BabylonJS official package; stable false positive for this ecosystem wrapper. | ai | |
| provenance | no-provenance | AI (provenance): Published via GitHub Actions; no provenance is common and not a risk signal for this package. | ai | |
| phantom-deps | phantom-dep:@babylonjs/havok | AI (phantom-deps): Havok is a peer/optional physics engine; config-only reference without direct import is expected for this type of wrapper package. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.0.92 | 5 / 22 | |
| 1.0.84 | 5 / 22 | |
| 1.0.83 | 5 / 20 | |
| 1.0.82 | 5 / 20 | |
| 1.0.79 | 5 / 20 | |
| 1.0.77 | 5 / 20 | |
| 1.0.75 | 5 / 20 | |
| 1.0.74 | 5 / 20 | |
| 1.0.73 | 5 / 20 | |
| 1.0.72 | 4 / 20 | |
| 1.0.39 | 4 / 18 | |
| 1.0.18 | 4 / 18 |
v1.0.92
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.84
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.82
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.79
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.77
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.74
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.73
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.39
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.18
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.