@quenty/softshutdown
This service lets you shut down servers without losing a bunch of players. When game.OnClose is called, the script teleports everyone in the server into a reserved server.
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established quenty/NevermoreEngine monorepo; provenance not used across the entire package family. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox/Lua package; JS static analysis cannot detect Lua imports. False positive for this monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/math | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/blend | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/table | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/basicpane | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/datastore | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard pnpm-enforcement preinstall; stable across all NevermoreEngine packages. | ai | |
| phantom-deps | phantom-dep:@quenty/servicebag | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/uiobjectutils | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/attributeutils | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/coreguienabler | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/valuebaseutils | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/clienttranslator | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/bindtocloseservice | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/teleportserviceutils | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Same as above — Lua imports not detectable by JS analyzer. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 9.45.2 | 19 / 0 | |
| 9.41.0 | 19 / 0 | |
| 9.38.1 | 19 / 0 | |
| 9.27.0 | 19 / 0 | |
| 9.26.0 | 19 / 0 | |
| 9.25.0 | 19 / 0 | |
| 9.24.0 | 19 / 0 |
v9.45.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.
v9.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.38.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v9.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.26.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.25.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v9.24.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.