@quenty/basicpane
Base UI object with visibility and a maid
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Publisher has 887 approved packages and a clean history; dormancy gap is not indicative of takeover for this well-established monorepo package. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Same-org monorepo package; Roblox/Lua packages may not use standard JS imports detectable by the analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/brio | AI (phantom-deps): Same-org monorepo package; Roblox/Lua packages may not use standard JS imports detectable by the analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same-org monorepo package; Roblox/Lua packages may not use standard JS imports detectable by the analyzer. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): only-allow pnpm is a standard package manager enforcement pattern; stable across all versions of this monorepo package. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Same-org monorepo package; Roblox/Lua packages may not use standard JS imports detectable by the analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/ducktype | AI (phantom-deps): Same-org monorepo package; Roblox/Lua packages may not use standard JS imports detectable by the analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same-org monorepo package; Roblox/Lua packages may not use standard JS imports detectable by the analyzer. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo package; Roblox/Lua packages may not use standard JS imports detectable by the analyzer. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 13.31.0 | 7 / 0 | |
| 13.30.2 | 7 / 0 | |
| 13.30.1 | 7 / 0 | |
| 13.30.0 | 7 / 0 | |
| 13.29.0 | 7 / 0 | |
| 13.28.0 | 7 / 0 | |
| 13.25.1 | 7 / 0 | |
| 13.25.0 | 7 / 0 | |
| 13.23.1 | 7 / 0 | |
| 13.22.1 | 7 / 0 | |
| 13.21.7 | 7 / 0 | |
| 13.21.3 | 7 / 0 | |
| 13.21.0 | 7 / 0 | |
| 13.20.0 | 7 / 0 | |
| 13.18.1 | 7 / 0 | |
| 13.18.0 | 7 / 0 |
v13.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.30.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.
v13.30.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.
v13.30.0
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.
v13.29.0
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.
v13.28.0
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.
v13.25.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.
v13.25.0
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.
v13.23.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.
v13.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.21.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.