@quenty/spawning MIT 26 versions

@quenty/spawning

npm Repository Homepage

Centralized spawning system

26

Versions

MIT

License

Yes

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

quenty

Keywords

RobloxNevermoreLua

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 monorepo package-manager enforcement pattern; stable for this package.	ai	2026/05/19
phantom-deps	phantom-dep:@quenty/maid	AI (phantom-deps): Roblox/Lua package; JS static analysis cannot detect Lua imports. Same-org dep, stable false positive.	ai	2026/05/19
phantom-deps	phantom-dep:@quenty/binder	AI (phantom-deps): Same-org Lua package; phantom-dep is a stable false positive for this ecosystem.	ai	2026/05/19
phantom-deps	phantom-dep:@quenty/loader	AI (phantom-deps): Same-org Lua package; phantom-dep is a stable false positive for this ecosystem.	ai	2026/05/19
phantom-deps	phantom-dep:@quentystudios/t	AI (phantom-deps): Roblox/Lua package; JS static analysis cannot detect Lua imports. Stable false positive.	ai	2026/05/19
phantom-deps	phantom-dep:@quenty/raycaster	AI (phantom-deps): Same-org Lua package; phantom-dep is a stable false positive for this ecosystem.	ai	2026/05/19
phantom-deps	phantom-dep:@quenty/servicebag	AI (phantom-deps): Same-org Lua package; phantom-dep is a stable false positive for this ecosystem.	ai	2026/05/19
phantom-deps	phantom-dep:@quenty/cmdrservice	AI (phantom-deps): Same-org Lua package; phantom-dep is a stable false positive for this ecosystem.	ai	2026/05/19
phantom-deps	phantom-dep:@quenty/randomutils	AI (phantom-deps): Same-org Lua package; phantom-dep is a stable false positive for this ecosystem.	ai	2026/05/19

Versions (showing 26 of 26)

Version	Deps	Published
10.43.2	8 / 0	2026-04-30
10.43.0	8 / 0	2026-04-23
10.34.1	8 / 0	2026-01-12
10.33.1	8 / 0	2026-01-10
10.33.0	8 / 0	2026-01-08
10.32.0	8 / 0	2026-01-06
10.31.1	8 / 0	2026-01-05
10.31.0	8 / 0	2026-01-04
10.30.8	8 / 0	2026-01-03
10.30.7	8 / 0	2025-12-31
10.30.6	7 / 0	2025-12-29
10.30.5	7 / 0	2025-12-29
10.30.4	7 / 0	2025-12-28
10.30.3	7 / 0	2025-12-11
10.30.2	7 / 0	2025-11-22
10.30.1	7 / 0	2025-11-12
10.30.0	7 / 0	2025-11-07
10.29.0	7 / 0	2025-10-08
10.28.0	7 / 0	2025-10-03
10.27.0	7 / 0	2025-10-01
10.26.0	7 / 0	2025-09-26
10.25.1	7 / 0	2025-09-15
10.25.0	7 / 0	2025-08-29
10.24.1	7 / 0	2025-08-12
10.24.0	7 / 0	2025-05-12
10.23.0	7 / 0	2025-05-10

v10.43.2

2 findings

HIGH Package has 'preinstall' script install-scripts

Script: npx only-allow pnpm

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.43.0

2 findings

HIGH Package has 'preinstall' script install-scripts

Script: npx only-allow pnpm

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.34.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.33.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.33.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.32.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.31.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.31.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.30.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.30.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.30.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.30.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.30.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.30.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.30.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.30.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v10.30.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.29.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.28.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.27.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.26.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.25.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.25.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.24.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.24.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v10.23.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.