@conduit-client/unstable-test
Luvio Next unstable test utilities
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@conduit-client/service-dedupe | AI (dependencies): Same-org sibling dep; consistent pattern across all @conduit-client package versions. | ai | |
| dependencies | unvetted-dep:@conduit-client/service-cache-policy | AI (dependencies): Same-org sibling dep; consistent pattern across all @conduit-client package versions. | ai | |
| dependencies | unvetted-dep:@conduit-client/service-type-registry | AI (dependencies): Same-org sibling dep; consistent pattern across all @conduit-client package versions. | ai | |
| dependencies | unvetted-dep:@conduit-client/service-cache-inclusion-policy-unstable | AI (dependencies): Same-org sibling dep; consistent pattern across all @conduit-client package versions. | ai | |
| provenance | no-provenance | AI (provenance): Consistent across all @conduit-client packages from this publisher; not a risk signal for this org. | ai | |
| phantom-deps | phantom-dep:@conduit-client/command-base | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic false positive for monorepo transitive usage. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal Salesforce monorepo package; sparse README and no keywords are expected for org-internal utilities. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 3.20.0 | 9 / 0 | |
| 3.19.4 | 9 / 0 | |
| 3.19.2 | 9 / 0 | |
| 3.19.0 | 9 / 0 | |
| 3.18.0 | 9 / 0 | |
| 3.17.3 | 9 / 0 | |
| 3.17.0 | 9 / 0 | |
| 3.13.1 | 9 / 0 | |
| 3.12.0 | 9 / 0 | |
| 3.10.0 | 9 / 0 | |
| 3.8.0 | 9 / 0 | |
| 3.7.1 | 9 / 0 | |
| 3.6.3 | 9 / 0 | |
| 3.6.2 | 9 / 0 | |
| 3.5.0 | 9 / 0 | |
| 3.4.0 | 9 / 0 | |
| 3.0.0 | 9 / 0 | |
| 2.1.0 | 9 / 0 |
v3.20.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.19.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.19.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.