@types/rx-lite-async
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@types/rx-lite | AI (phantom-deps): DefinitelyTyped type packages conventionally declare peer type dependencies without direct imports; this is expected and benign for @types/* packages. | ai | |
| dependencies | unvetted-dep:@types/rx-lite | AI (dependencies): @types/rx-lite is a sibling DefinitelyTyped package; the wildcard version constraint is standard practice for @types/* inter-dependencies. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 4.0.5 | 1 / 0 | |
| 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.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.