@quenty/particleengine
Adds GUI based particle engine to Roblox
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 |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a benign package-manager enforcement script; stable pattern across this monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/table | AI (phantom-deps): Same-org monorepo sibling; indirect imports are expected in this package structure. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo sibling; indirect imports are expected in this package structure. | ai | |
| phantom-deps | phantom-dep:@quenty/remoting | AI (phantom-deps): Same-org monorepo sibling; indirect imports are expected in this package structure. | ai | |
| phantom-deps | phantom-dep:@quenty/servicebag | AI (phantom-deps): Same-org monorepo sibling; indirect imports are expected in this package structure. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 13.40.0 | 4 / 0 | |
| 13.31.2 | 4 / 0 | |
| 13.30.0 | 4 / 0 | |
| 13.29.0 | 4 / 0 | |
| 13.23.2 | 4 / 0 | |
| 13.23.1 | 4 / 0 | |
| 13.23.0 | 4 / 0 | |
| 13.22.0 | 4 / 0 | |
| 13.21.6 | 4 / 0 | |
| 13.21.5 | 4 / 0 | |
| 13.21.4 | 3 / 0 | |
| 13.21.3 | 3 / 0 | |
| 13.21.2 | 3 / 0 | |
| 13.21.1 | 3 / 0 | |
| 13.21.0 | 3 / 0 | |
| 13.20.0 | 3 / 0 | |
| 13.19.1 | 3 / 0 | |
| 13.19.0 | 3 / 0 | |
| 13.18.3 | 3 / 0 | |
| 13.18.2 | 3 / 0 | |
| 13.18.1 | 3 / 0 | |
| 13.18.0 | 3 / 0 | |
| 13.17.2 | 3 / 0 | |
| 13.17.1 | 3 / 0 | |
| 13.17.0 | 3 / 0 | |
| 13.16.0 | 3 / 0 | |
| 13.15.0 | 3 / 0 | |
| 13.14.0 | 3 / 0 | |
| 13.13.0 | 3 / 0 | |
| 13.12.1 | 3 / 0 | |
| 13.12.0 | 3 / 0 | |
| 13.11.0 | 3 / 0 | |
| 13.10.1 | 3 / 0 | |
| 13.10.0 | 3 / 0 | |
| 13.9.1 | 3 / 0 | |
| 13.9.0 | 3 / 0 | |
| 13.8.0 | 3 / 0 | |
| 13.7.0 | 3 / 0 | |
| 13.6.0 | 3 / 0 | |
| 13.5.0 | 3 / 0 | |
| 13.4.1 | 3 / 0 | |
| 13.4.0 | 3 / 0 |
v13.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.