@rxweave/cli
The `rxweave` CLI — init, dev, emit, stream, query, inspect, registry. AI-agent-friendly (NDJSON I/O, no prompts).
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): Scoped @rxweave/cli bears no resemblance to 'joi'; edit-distance match is spurious. | ai | |
| phantom-deps | phantom-dep:@rxweave/reactive | AI (phantom-deps): Same-org sibling dep in a monorepo; declared for re-export or transitive use. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.5.5 | 12 / 4 | |
| 0.5.4 | 12 / 4 | |
| 0.5.3 | 12 / 4 | |
| 0.5.2 | 12 / 4 | |
| 0.5.1 | 12 / 4 | |
| 0.5.0 | 12 / 4 | |
| 0.4.1 | 12 / 4 | |
| 0.4.0 | 12 / 4 | |
| 0.3.0 | 11 / 4 |
v0.5.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.