@quenty/clipcharacters
Clip characters locally on the client of other clients so they don't interfer with physics.
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 |
|---|---|---|---|---|
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard package manager enforcement script; stable across all versions of this monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/brio | AI (phantom-deps): Roblox/Lua monorepo; Lua modules not directly imported by JS tooling — stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same as above — Lua monorepo false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/table | AI (phantom-deps): Same as above — Lua monorepo false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same as above — Lua monorepo false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/remoting | AI (phantom-deps): Same as above — Lua monorepo false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Same as above — Lua monorepo false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/servicebag | AI (phantom-deps): Same as above — Lua monorepo false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/statestack | AI (phantom-deps): Same as above — Lua monorepo false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/playerutils | AI (phantom-deps): Same as above — Lua monorepo false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same as above — Lua monorepo false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/characterutils | AI (phantom-deps): Same as above — Lua monorepo false positive. | ai | |
| phantom-deps | phantom-dep:@quentystudios/jest-lua | AI (phantom-deps): Test dependency referenced in config; Lua monorepo pattern, stable false positive. | ai | |
| phantom-deps | phantom-dep:@quenty/nevermore-test-runner | AI (phantom-deps): Same as above — Lua monorepo false positive. | ai |
Versions (showing 23 of 23)
| Version | Deps | Published |
|---|---|---|
| 12.39.0 | 13 / 0 | |
| 12.37.2 | 13 / 0 | |
| 12.36.0 | 13 / 0 | |
| 12.29.0 | 11 / 0 | |
| 12.28.0 | 11 / 0 | |
| 12.27.1 | 11 / 0 | |
| 12.27.0 | 11 / 0 | |
| 12.26.8 | 11 / 0 | |
| 12.26.7 | 11 / 0 | |
| 12.26.6 | 11 / 0 | |
| 12.26.5 | 11 / 0 | |
| 12.26.4 | 11 / 0 | |
| 12.26.3 | 11 / 0 | |
| 12.26.2 | 11 / 0 | |
| 12.26.1 | 11 / 0 | |
| 12.26.0 | 11 / 0 | |
| 12.25.0 | 11 / 0 | |
| 12.24.0 | 11 / 0 | |
| 12.23.0 | 11 / 0 | |
| 12.22.1 | 11 / 0 | |
| 12.22.0 | 11 / 0 | |
| 12.21.0 | 11 / 0 | |
| 12.20.0 | 11 / 0 |
v12.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.37.2
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.36.0
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.29.0
2 findingsScript: npx only-allow pnpm
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.28.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.27.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.26.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.26.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.26.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.26.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.26.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.26.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.26.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.26.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.