@babylonjs/node-particle-editor
The Node Particle Editor is a visual tool for creating and editing particle systems using a node-based graph in Babylon.js.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/babylon.nodeParticleEditor.js | AI (source-diff): Standard minified UMD rollup bundle for a BabylonJS editor tool; not obfuscated malware. | ai | |
| source-diff | obfuscated-file:dist/babylon.nodeParticleEditor.max.js | AI (source-diff): Standard minified UMD rollup bundle for a BabylonJS editor tool; not obfuscated malware. | ai | |
| source-diff | net-exec-file:dist/babylon.nodeParticleEditor.js | AI (source-diff): Network/exec pattern is from bundled React+BabylonJS library code, not dropper behavior. | ai | |
| source-diff | net-exec-file:dist/babylon.nodeParticleEditor.max.js | AI (source-diff): Network/exec pattern is from bundled React+BabylonJS library code, not dropper behavior. | ai | |
| source-diff | encoded-string-file:dist/babylon.nodeParticleEditor.js | AI (source-diff): Long strings are webpack-bundled CSS/JS, not obfuscated payloads; stable pattern for this package. | ai | |
| source-diff | encoded-string-file:dist/babylon.nodeParticleEditor.max.js | AI (source-diff): Same webpack bundle pattern; stable false positive for this package. | ai |
Versions (showing 7 of 107)
| Version | Deps | Published |
|---|---|---|
| 8.37.2 | 0 / 3 | |
| 8.37.1 | 0 / 3 | |
| 8.37.0 | 0 / 3 | |
| 8.36.1 | 0 / 3 | |
| 8.36.0 | 0 / 3 | |
| 8.35.0 | 0 / 3 | |
| 8.34.1 | 0 / 3 |
v8.37.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.37.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.37.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.36.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.36.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.35.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.34.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.