@quenty/guivisiblemanager
Help manage the visibility of GUIs while only constructing the Gui while visible
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 versions of this monorepo package. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same-org monorepo package; Nevermore uses a custom Lua loader, not direct JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo package; Nevermore uses a custom Lua loader, not direct JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Same-org monorepo package; Nevermore uses a custom Lua loader, not direct JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same-org monorepo package; Nevermore uses a custom Lua loader, not direct JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/basicpane | AI (phantom-deps): Same-org monorepo package; Nevermore uses a custom Lua loader, not direct JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/baseobject | AI (phantom-deps): Same-org monorepo package; Nevermore uses a custom Lua loader, not direct JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same-org monorepo package; Nevermore uses a custom Lua loader, not direct JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/cancellabledelay | AI (phantom-deps): Same-org monorepo package; Nevermore uses a custom Lua loader, not direct JS imports. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 12.22.2 | 8 / 0 | |
| 12.22.1 | 8 / 0 | |
| 12.15.1 | 8 / 0 | |
| 12.15.0 | 8 / 0 | |
| 12.14.1 | 8 / 0 | |
| 12.14.0 | 8 / 0 | |
| 12.13.7 | 8 / 0 | |
| 12.13.6 | 8 / 0 | |
| 12.13.5 | 5 / 0 | |
| 12.13.4 | 5 / 0 | |
| 12.13.3 | 5 / 0 | |
| 12.13.2 | 5 / 0 | |
| 12.13.1 | 5 / 0 | |
| 12.13.0 | 5 / 0 | |
| 12.12.0 | 5 / 0 | |
| 12.11.0 | 5 / 0 | |
| 12.10.1 | 5 / 0 | |
| 12.10.0 | 5 / 0 |
v12.22.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.
v12.22.1
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.
v12.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.13.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.13.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v12.13.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v12.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.