@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, 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): 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 38 of 38)
| 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 | |
| 5.19.3 | 4 / 0 | |
| 5.19.2 | 4 / 0 | |
| 5.19.1 | 4 / 0 | |
| 5.19.0 | 4 / 0 | |
| 5.18.2 | 4 / 0 | |
| 5.18.1 | 4 / 0 | |
| 5.18.0 | 4 / 0 | |
| 5.17.0 | 4 / 0 | |
| 5.16.0 | 4 / 0 | |
| 5.15.0 | 4 / 0 | |
| 5.14.0 | 4 / 0 | |
| 5.13.1 | 4 / 0 | |
| 5.13.0 | 4 / 0 | |
| 5.12.0 | 4 / 0 | |
| 5.11.1 | 4 / 0 | |
| 5.11.0 | 4 / 0 | |
| 5.10.1 | 4 / 0 | |
| 5.10.0 | 4 / 0 | |
| 5.9.0 | 4 / 0 | |
| 5.8.0 | 4 / 0 | |
| 5.7.0 | 4 / 0 | |
| 5.6.0 | 4 / 0 | |
| 5.5.0 | 4 / 0 | |
| 5.4.0 | 4 / 0 |
v5.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.