@quenty/assetserviceutils
Provides a wrapper for AssetService's async calls
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): only-allow pnpm is a standard monorepo package manager enforcement; stable for this package. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@quenty/memoize | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@quenty/promise | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@quenty/servicebag | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic is a false positive here. | ai | |
| phantom-deps | phantom-dep:@quenty/instanceutils | AI (phantom-deps): Same-org monorepo dependency; phantom-dep heuristic is a false positive here. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 5.31.2 | 5 / 0 | |
| 5.24.0 | 5 / 0 | |
| 5.23.0 | 5 / 0 | |
| 5.22.6 | 5 / 0 | |
| 5.22.5 | 5 / 0 | |
| 5.22.4 | 4 / 0 | |
| 5.22.3 | 4 / 0 | |
| 5.22.2 | 4 / 0 | |
| 5.22.1 | 4 / 0 | |
| 5.22.0 | 4 / 0 | |
| 5.21.0 | 4 / 0 | |
| 5.20.2 | 4 / 0 | |
| 5.20.1 | 4 / 0 | |
| 5.20.0 | 4 / 0 |
v5.31.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.
v5.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.