@quenty/rxsignal
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 package-manager enforcement script; stable across all versions of this monorepo package. | ai | |
| phantom-deps | phantom-dep:@quenty/rx | AI (phantom-deps): Same-org Roblox/Lua package; phantom-dep heuristic unreliable for Lua tooling packages. | ai | |
| phantom-deps | phantom-dep:@quenty/loader | AI (phantom-deps): Same-org Roblox/Lua package; phantom-dep heuristic unreliable for Lua tooling packages. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 7.28.0 | 2 / 0 | |
| 7.27.0 | 2 / 0 | |
| 7.21.0 | 2 / 0 | |
| 7.20.4 | 2 / 0 | |
| 7.20.3 | 2 / 0 | |
| 7.20.2 | 2 / 0 | |
| 7.20.1 | 2 / 0 | |
| 7.20.0 | 2 / 0 | |
| 7.19.0 | 2 / 0 | |
| 7.18.1 | 2 / 0 | |
| 7.18.0 | 2 / 0 |
v7.27.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.