@quenty/seatutils
Holds utilities to work with Roblox seats
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Quenty monorepo publishes in bulk; dormancy between release cycles is normal for this org. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/brio | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic false positive for this package. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a standard monorepo package-manager enforcement; stable across all versions of this package. | ai | |
| phantom-deps | phantom-dep:@quenty/instanceutils | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/characterutils | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/statestack | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 7.34.0 | 6 / 0 | |
| 7.33.2 | 6 / 0 | |
| 7.33.1 | 6 / 0 | |
| 7.33.0 | 6 / 0 | |
| 7.31.0 | 6 / 0 | |
| 7.30.0 | 6 / 0 | |
| 7.28.1 | 6 / 0 | |
| 7.28.0 | 6 / 0 | |
| 7.26.2 | 6 / 0 | |
| 7.26.1 | 6 / 0 | |
| 7.24.2 | 6 / 0 | |
| 7.21.1 | 6 / 0 | |
| 7.21.0 | 6 / 0 | |
| 7.20.0 | 6 / 0 |
v7.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.33.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.
v7.33.1
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.
v7.33.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.
v7.31.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.
v7.30.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.
v7.28.1
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.
v7.28.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.
v7.26.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.
v7.26.1
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.
v7.24.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.