@types/rx-lite-testing
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:@types/rx-lite-virtualtime | AI (dependencies): Standard DefinitelyTyped inter-package dependency; @types packages routinely depend on related @types packages. Not a risk for this package family. | ai | |
| phantom-deps | phantom-dep:@types/rx-lite-virtualtime | AI (phantom-deps): Type definition packages are loaded by convention, not direct imports. Phantom-dep finding is a stable false positive for @types/* packages. | ai | |
| provenance | no-provenance | AI (provenance): DefinitelyTyped packages published via the types publisher do not use Sigstore provenance; this is consistent across all versions and not a risk signal. | ai |
Versions (showing 5 of 5)
| Version | Deps | Published |
|---|---|---|
| 4.0.4 | 1 / 0 | |
| 4.0.3 | 1 / 0 | |
| 4.0.2 | 1 / 0 | |
| 4.0.1 | 1 / 0 | |
| 4.0.0 | 1 / 0 |
v4.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.