@quenty/parttouchingcalculator
Determines if parts are touching or not
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 |
|---|---|---|---|---|
| publish-pattern | rapid-publish | AI (publish-pattern): Monorepo release automation publishes many sibling packages in quick succession. | ai | |
| phantom-deps | phantom-dep:@quenty/qgui | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for Roblox/Lua packages. | ai | |
| phantom-deps | phantom-dep:@quenty/binder | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for Roblox/Lua packages. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a standard monorepo package-manager enforcement pattern; stable across all @quenty/* packages. | ai | |
| phantom-deps | phantom-dep:@quenty/characterutils | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for Roblox/Lua packages. | ai | |
| phantom-deps | phantom-dep:@quenty/boundingboxutils | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for Roblox/Lua packages. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic unreliable for Roblox/Lua packages. | ai |
Versions (showing 50 of 50)
| Version | Deps | Published |
|---|---|---|
| 14.48.0 | 5 / 0 | |
| 14.47.0 | 5 / 0 | |
| 14.38.2 | 5 / 0 | |
| 14.32.0 | 5 / 0 | |
| 14.31.0 | 5 / 0 | |
| 14.30.0 | 5 / 0 | |
| 14.29.1 | 5 / 0 | |
| 14.29.0 | 5 / 0 | |
| 14.28.4 | 5 / 0 | |
| 14.28.3 | 5 / 0 | |
| 14.28.2 | 5 / 0 | |
| 14.28.1 | 5 / 0 | |
| 14.28.0 | 5 / 0 | |
| 14.27.3 | 5 / 0 | |
| 14.27.2 | 5 / 0 | |
| 14.27.1 | 5 / 0 | |
| 14.27.0 | 5 / 0 | |
| 14.26.0 | 5 / 0 | |
| 14.25.0 | 5 / 0 | |
| 14.24.0 | 5 / 0 | |
| 14.23.1 | 5 / 0 | |
| 14.23.0 | 5 / 0 | |
| 14.22.0 | 5 / 0 | |
| 14.21.0 | 5 / 0 | |
| 14.20.3 | 5 / 0 | |
| 14.20.2 | 5 / 0 | |
| 14.20.1 | 5 / 0 | |
| 14.20.0 | 5 / 0 | |
| 14.19.2 | 5 / 0 | |
| 14.19.1 | 5 / 0 | |
| 14.19.0 | 5 / 0 | |
| 14.18.0 | 5 / 0 | |
| 14.17.0 | 5 / 0 | |
| 14.16.0 | 5 / 0 | |
| 14.15.0 | 5 / 0 | |
| 14.14.0 | 5 / 0 | |
| 14.13.0 | 5 / 0 | |
| 14.12.1 | 5 / 0 | |
| 14.12.0 | 5 / 0 | |
| 14.11.0 | 5 / 0 | |
| 14.10.2 | 5 / 0 | |
| 14.10.1 | 5 / 0 | |
| 14.10.0 | 5 / 0 | |
| 14.9.1 | 5 / 0 | |
| 14.9.0 | 5 / 0 | |
| 14.8.0 | 5 / 0 | |
| 14.7.0 | 5 / 0 | |
| 14.6.0 | 5 / 0 | |
| 14.5.0 | 5 / 0 | |
| 14.4.0 | 5 / 0 |
v14.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v14.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.