@quenty/actionmanager
Holds single toggleable actions (like a tool system)
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): npx only-allow pnpm is a standard pnpm-enforcement pattern used across the NevermoreEngine monorepo; not malicious. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic is a false positive for Lua/Roblox packages that don't use JS imports. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo dependency; false positive for Lua/Roblox packages. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Same-org monorepo dependency; false positive for Lua/Roblox packages. | ai | |
| phantom-deps | phantom-dep:@quenty/valueobject | AI (phantom-deps): Same-org monorepo dependency; false positive for Lua/Roblox packages. | ai | |
| phantom-deps | phantom-dep:@quenty/enabledmixin | AI (phantom-deps): Same-org monorepo dependency; false positive for Lua/Roblox packages. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 13.32.2 | 5 / 0 | |
| 13.25.0 | 5 / 0 | |
| 13.24.1 | 5 / 0 | |
| 13.24.0 | 5 / 0 | |
| 13.23.7 | 5 / 0 | |
| 13.23.6 | 5 / 0 | |
| 13.23.5 | 5 / 0 | |
| 13.23.4 | 5 / 0 | |
| 13.23.3 | 5 / 0 | |
| 13.23.2 | 5 / 0 | |
| 13.23.1 | 5 / 0 | |
| 13.23.0 | 5 / 0 | |
| 13.22.0 | 5 / 0 | |
| 13.21.0 | 5 / 0 | |
| 13.20.1 | 5 / 0 | |
| 13.20.0 | 5 / 0 |
v13.32.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.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.24.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.23.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.23.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.23.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.22.0
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.1
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.