@quenty/enabledmixin
Adds Enabled/Disabled state to class
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 strong track record; dormancy gap is not indicative of takeover for this org. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Same-org Lua/Roblox package; phantom-dep heuristic doesn't apply to this ecosystem's module resolution. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same-org Lua/Roblox package; phantom-dep heuristic doesn't apply to this ecosystem's module resolution. | ai | |
| install-scripts | install-script:preinstall | AI (install-scripts): npx only-allow pnpm is a standard pnpm-enforcement preinstall; stable pattern across this monorepo. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Same-org Lua/Roblox package; phantom-dep heuristic doesn't apply to this ecosystem's module resolution. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same-org Lua/Roblox package; phantom-dep heuristic doesn't apply to this ecosystem's module resolution. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org Lua/Roblox package; phantom-dep heuristic doesn't apply to this ecosystem's module resolution. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 11.26.0 | 5 / 0 | |
| 11.25.2 | 5 / 0 | |
| 11.25.1 | 5 / 0 | |
| 11.25.0 | 5 / 0 | |
| 11.24.0 | 5 / 0 | |
| 11.20.1 | 5 / 0 | |
| 11.20.0 | 5 / 0 | |
| 11.18.0 | 5 / 0 | |
| 11.16.4 | 5 / 0 | |
| 11.16.2 | 5 / 0 | |
| 11.16.0 | 5 / 0 | |
| 11.15.0 | 5 / 0 | |
| 11.14.0 | 5 / 0 | |
| 11.13.1 | 5 / 0 | |
| 11.13.0 | 5 / 0 |
v11.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v11.25.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.
v11.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.
v11.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.
v11.24.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.
v11.20.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.
v11.20.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.
v11.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.16.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.16.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v11.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.