@quenty/valuebaseutils
Provides utilities for working with valuesbase objects, like IntValue or ObjectValue in Roblox.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
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 used across all @quenty/* packages. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Roblox Lua package; imports may not be detectable by standard JS import analysis. | ai | |
| phantom-deps | phantom-dep:@quenty/brio | AI (phantom-deps): Roblox Lua package; imports may not be detectable by standard JS import analysis. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Roblox Lua package; imports may not be detectable by standard JS import analysis. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Roblox Lua package; imports may not be detectable by standard JS import analysis. | ai | |
| phantom-deps | phantom-dep:@quenty/rxsignal | AI (phantom-deps): Roblox Lua package; imports may not be detectable by standard JS import analysis. | ai | |
| phantom-deps | phantom-dep:@quenty/instanceutils | AI (phantom-deps): Roblox Lua package; imports may not be detectable by standard JS import analysis. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 13.29.0 | 6 / 0 | |
| 13.28.0 | 6 / 0 | |
| 13.22.0 | 6 / 0 | |
| 13.21.0 | 6 / 0 | |
| 13.20.7 | 6 / 0 | |
| 13.20.6 | 6 / 0 | |
| 13.20.5 | 6 / 0 | |
| 13.20.4 | 6 / 0 | |
| 13.20.3 | 6 / 0 | |
| 13.20.2 | 6 / 0 | |
| 13.20.1 | 6 / 0 | |
| 13.20.0 | 6 / 0 | |
| 13.19.0 | 6 / 0 | |
| 13.18.1 | 6 / 0 | |
| 13.18.0 | 6 / 0 | |
| 13.17.3 | 6 / 0 | |
| 13.17.2 | 6 / 0 | |
| 13.17.1 | 6 / 0 | |
| 13.17.0 | 6 / 0 | |
| 13.16.2 | 6 / 0 | |
| 13.16.1 | 6 / 0 | |
| 13.16.0 | 6 / 0 | |
| 13.15.0 | 6 / 0 | |
| 13.14.0 | 6 / 0 | |
| 13.13.0 | 6 / 0 | |
| 13.12.0 | 6 / 0 | |
| 13.11.1 | 6 / 0 | |
| 13.11.0 | 6 / 0 | |
| 13.10.0 | 6 / 0 | |
| 13.9.1 | 6 / 0 | |
| 13.9.0 | 6 / 0 | |
| 13.8.1 | 6 / 0 | |
| 13.8.0 | 6 / 0 | |
| 13.7.0 | 6 / 0 | |
| 13.6.0 | 6 / 0 | |
| 13.5.0 | 6 / 0 | |
| 13.4.0 | 6 / 0 | |
| 13.3.0 | 6 / 0 | |
| 13.2.0 | 6 / 0 | |
| 13.1.0 | 6 / 0 | |
| 13.0.0 | 6 / 0 |
v13.22.0
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.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.20.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.20.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.20.1
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. Consider requesting the maintainer enable provenance via CI/CD.
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.
v13.17.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v13.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v13.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.