@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, 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 releases many sibling packages together; expected cadence. | ai | |
| 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/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 | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Same-org monorepo sibling; phantom-dep heuristic false positive for this package. | ai |
Versions (showing 54 of 54)
| Version | Deps | Published |
|---|---|---|
| 7.40.0 | 6 / 0 | |
| 7.39.0 | 6 / 0 | |
| 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.26.0 | 6 / 0 | |
| 7.25.1 | 6 / 0 | |
| 7.25.0 | 6 / 0 | |
| 7.24.7 | 6 / 0 | |
| 7.24.6 | 6 / 0 | |
| 7.24.5 | 6 / 0 | |
| 7.24.4 | 6 / 0 | |
| 7.24.3 | 6 / 0 | |
| 7.24.2 | 6 / 0 | |
| 7.24.1 | 6 / 0 | |
| 7.24.0 | 6 / 0 | |
| 7.23.0 | 6 / 0 | |
| 7.22.0 | 6 / 0 | |
| 7.21.1 | 6 / 0 | |
| 7.21.0 | 6 / 0 | |
| 7.20.0 | 6 / 0 | |
| 7.19.3 | 6 / 0 | |
| 7.19.2 | 6 / 0 | |
| 7.19.1 | 6 / 0 | |
| 7.19.0 | 6 / 0 | |
| 7.18.2 | 6 / 0 | |
| 7.18.1 | 6 / 0 | |
| 7.18.0 | 6 / 0 | |
| 7.17.0 | 6 / 0 | |
| 7.16.0 | 6 / 0 | |
| 7.15.0 | 6 / 0 | |
| 7.14.0 | 6 / 0 | |
| 7.13.0 | 6 / 0 | |
| 7.12.1 | 6 / 0 | |
| 7.12.0 | 6 / 0 | |
| 7.11.0 | 6 / 0 | |
| 7.10.2 | 6 / 0 | |
| 7.10.1 | 6 / 0 | |
| 7.10.0 | 6 / 0 | |
| 7.9.1 | 6 / 0 | |
| 7.9.0 | 6 / 0 | |
| 7.8.0 | 6 / 0 | |
| 7.7.0 | 6 / 0 | |
| 7.6.0 | 6 / 0 | |
| 7.5.0 | 6 / 0 | |
| 7.4.0 | 6 / 0 | |
| 7.3.0 | 6 / 0 |
v7.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.