@quenty/studio-bridge
WebSocket-based bridge for running Luau scripts in Roblox Studio
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:silent-process-exec | AI (semgrep): Spawns Roblox Studio GUI executable detached; expected behavior for a Studio bridge CLI tool. | ai | |
| semgrep | semgrep:silent-process-exec-var | AI (semgrep): Same spawn call as silent-process-exec; launching Studio GUI detached is intentional. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Decodes binary field from structured result data; not obfuscated payload handling. | ai | |
| semgrep | semgrep:env-spread | AI (semgrep): Fires in a test file to snapshot/restore process.env — standard test pattern, not exfiltration. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 0.15.0 | 7 / 5 | |
| 0.14.0 | 7 / 5 | |
| 0.13.0 | 7 / 5 | |
| 0.12.0 | 7 / 5 | |
| 0.11.0 | 7 / 5 | |
| 0.10.0 | 7 / 5 | |
| 0.9.0 | 7 / 5 | |
| 0.8.0 | 7 / 5 | |
| 0.7.1 | 6 / 5 | |
| 0.7.0 | 6 / 5 | |
| 0.6.0 | 6 / 5 | |
| 0.5.0 | 6 / 5 | |
| 0.4.0 | 6 / 5 | |
| 0.3.0 | 6 / 5 | |
| 0.2.2 | 6 / 5 | |
| 0.2.1 | 6 / 5 | |
| 0.2.0 | 6 / 5 |
v0.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
3 findingsSilent detached process — runs invisibly in the background (reverse shells, miners) 141 | OutputHelper.verbose(`[StudioBridge] ${studioExe} "${placePath}"`); 142 | > 143 | const proc = spawn(studioExe, placePath ? [placePath] : [], { 144 | detached: true, 145 | stdio: 'ignore',
Silent detached process — runs invisibly in the background (reverse shells, miners) 141 | OutputHelper.verbose(`[StudioBridge] ${studioExe} "${placePath}"`); 142 | > 143 | const proc = spawn(studioExe, placePath ? [placePath] : [], { 144 | detached: true, 145 | stdio: 'ignore',
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.