@quenty/valueobject
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 package manager enforcement pattern; stable for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox/Lua package; Node.js import detection is a false positive for this ecosystem. | ai | |
| phantom-deps | phantom-dep:@quenty/brio | AI (phantom-deps): Roblox/Lua package; Node.js import detection is a false positive for this ecosystem. | ai | |
| phantom-deps | phantom-dep:@quenty/maid | AI (phantom-deps): Roblox/Lua package; Node.js import detection is a false positive for this ecosystem. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Roblox/Lua package; Node.js import detection is a false positive for this ecosystem. | ai | |
| phantom-deps | phantom-dep:@quenty/signal | AI (phantom-deps): Roblox/Lua package; Node.js import detection is a false positive for this ecosystem. | ai | |
| phantom-deps | phantom-dep:@quenty/ducktype | AI (phantom-deps): Roblox/Lua package; Node.js import detection is a false positive for this ecosystem. | ai | |
| phantom-deps | phantom-dep:@quenty/valuebaseutils | AI (phantom-deps): Roblox/Lua package; Node.js import detection is a false positive for this ecosystem. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 13.30.0 | 7 / 0 | |
| 13.29.0 | 7 / 0 | |
| 13.23.0 | 7 / 0 | |
| 13.22.1 | 7 / 0 | |
| 13.22.0 | 7 / 0 | |
| 13.21.7 | 7 / 0 | |
| 13.21.6 | 7 / 0 | |
| 13.21.5 | 7 / 0 | |
| 13.21.4 | 7 / 0 | |
| 13.21.3 | 7 / 0 | |
| 13.21.2 | 7 / 0 | |
| 13.21.1 | 7 / 0 | |
| 13.21.0 | 7 / 0 | |
| 13.20.0 | 7 / 0 | |
| 13.19.0 | 7 / 0 | |
| 13.18.1 | 7 / 0 | |
| 13.18.0 | 7 / 0 |
v13.29.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.22.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v13.21.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.21.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.19.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.