@quenty/bindtocloseservice
Bind to game close API in a centralized location.
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): only-allow pnpm is a standard package manager enforcement script; stable across all @quenty/* packages. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Roblox/Lua loader pattern; deps loaded indirectly via @quenty/loader, not direct JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same org loader pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/symbol | AI (phantom-deps): Same org loader pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same org loader pattern; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/servicebag | AI (phantom-deps): Same org loader pattern; stable false positive for this package. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 8.30.0 | 5 / 2 | |
| 8.29.0 | 5 / 2 | |
| 8.23.0 | 5 / 2 | |
| 8.22.1 | 5 / 2 | |
| 8.22.0 | 5 / 2 | |
| 8.21.7 | 5 / 2 | |
| 8.21.6 | 5 / 2 | |
| 8.21.5 | 4 / 2 | |
| 8.21.4 | 4 / 2 | |
| 8.21.3 | 4 / 2 | |
| 8.21.2 | 4 / 2 | |
| 8.21.1 | 4 / 2 | |
| 8.21.0 | 4 / 2 | |
| 8.20.0 | 4 / 2 | |
| 8.19.0 | 4 / 2 | |
| 8.18.1 | 4 / 2 | |
| 8.18.0 | 4 / 2 |
v8.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.