starpc
Streaming protobuf RPC service protocol over any two-way channel.
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| install-scripts | install-script:postinstall | AI (install-scripts): postinstall runs 'go mod vendor' — safe Go dependency vendoring, stable for this hybrid Go/TS package. | ai | |
| provenance | slsa-provenance | AI (provenance): Package consistently published via CI with SLSA attestation; GitHub Actions publisher is expected. | ai | |
| provenance | publisher-changed | AI (provenance): Transition from paralin to GitHub Actions CI is consistent with SLSA-attested automated publishing pipeline. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): 191-day gap explained by CI/CD pipeline migration; SLSA attestation confirms legitimate publish. | ai | |
| dependencies | unvetted-dep:@aptre/yamux | AI (dependencies): Same org as starpc (Aperture Robotics); internal dep swap, stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@aptre/it-ws | AI (dependencies): First-party dependency from the same Aperture Robotics org as starpc itself. | ai | |
| dependencies | unvetted-dep:@aptre/protobuf-es-lite | AI (dependencies): First-party dependency from the same Aperture Robotics org as starpc itself. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): ws is a declared runtime dep used indirectly via isomorphic-ws; phantom-dep false positive stable for this package. | ai |
Versions (showing 100 of 200)
| Version | Deps | Published |
|---|---|---|
| 0.31.3 | 15 / 11 | |
| 0.31.2 | 15 / 13 | |
| 0.31.1 | 15 / 13 | |
| 0.31.0 | 15 / 13 | |
| 0.23.2 | 17 / 10 | |
| 0.23.1 | 17 / 10 | |
| 0.23.0 | 17 / 10 | |
| 0.22.8 | 17 / 10 | |
| 0.22.7 | 17 / 10 | |
| 0.22.6 | 17 / 10 | |
| 0.22.5 | 17 / 10 | |
| 0.22.4 | 17 / 14 | |
| 0.22.3 | 17 / 14 | |
| 0.22.2 | 17 / 14 | |
| 0.22.1 | 17 / 14 | |
| 0.22.0 | 17 / 14 | |
| 0.21.6 | 17 / 14 | |
| 0.21.5 | 17 / 14 | |
| 0.21.4 | 17 / 14 | |
| 0.21.3 | 17 / 14 | |
| 0.21.2 | 17 / 13 | |
| 0.21.1 | 17 / 13 | |
| 0.21.0 | 16 / 13 | |
| 0.20.1 | 18 / 13 | |
| 0.20.0 | 18 / 13 | |
| 0.19.3 | 18 / 13 | |
| 0.19.2 | 18 / 13 | |
| 0.19.1 | 18 / 13 | |
| 0.19.0 | 18 / 13 | |
| 0.18.3 | 18 / 13 | |
| 0.18.2 | 18 / 13 | |
| 0.18.1 | 18 / 13 | |
| 0.18.0 | 18 / 13 | |
| 0.17.1 | 18 / 13 | |
| 0.17.0 | 17 / 13 | |
| 0.16.1 | 17 / 13 | |
| 0.16.0 | 17 / 13 | |
| 0.15.4 | 17 / 13 | |
| 0.15.3 | 17 / 13 | |
| 0.15.2 | 17 / 12 | |
| 0.15.1 | 17 / 12 | |
| 0.15.0 | 17 / 12 | |
| 0.14.1 | 17 / 12 | |
| 0.14.0 | 17 / 12 | |
| 0.13.3 | 17 / 12 | |
| 0.13.2 | 17 / 12 | |
| 0.13.1 | 17 / 12 | |
| 0.13.0 | 17 / 12 | |
| 0.12.3 | 17 / 12 | |
| 0.12.2 | 17 / 12 | |
| 0.12.1 | 17 / 12 | |
| 0.12.0 | 17 / 12 | |
| 0.11.3 | 17 / 12 | |
| 0.11.2 | 17 / 12 | |
| 0.11.0 | 16 / 12 | |
| 0.10.9 | 16 / 12 | |
| 0.10.8 | 16 / 12 | |
| 0.10.7 | 16 / 12 | |
| 0.10.6 | 16 / 12 | |
| 0.10.5 | 16 / 12 | |
| 0.10.4 | 16 / 12 | |
| 0.10.3 | 16 / 12 | |
| 0.10.2 | 16 / 12 | |
| 0.10.1 | 16 / 12 | |
| 0.10.0 | 16 / 12 | |
| 0.9.2 | 16 / 12 | |
| 0.9.1 | 16 / 12 | |
| 0.9.0 | 16 / 12 | |
| 0.8.6 | 15 / 12 | |
| 0.8.5 | 15 / 12 | |
| 0.8.4 | 15 / 12 | |
| 0.8.3 | 15 / 12 | |
| 0.8.2 | 15 / 12 | |
| 0.8.1 | 15 / 12 | |
| 0.8.0 | 15 / 12 | |
| 0.7.1 | 15 / 12 | |
| 0.7.0 | 15 / 12 | |
| 0.6.2 | 15 / 12 | |
| 0.6.1 | 15 / 12 | |
| 0.6.0 | 15 / 12 | |
| 0.5.2 | 15 / 12 | |
| 0.5.1 | 15 / 12 | |
| 0.5.0 | 15 / 10 | |
| 0.4.9 | 15 / 10 | |
| 0.4.8 | 15 / 10 | |
| 0.4.7 | 15 / 10 | |
| 0.4.6 | 15 / 10 | |
| 0.4.5 | 15 / 10 | |
| 0.4.3 | 15 / 10 | |
| 0.4.2 | 15 / 10 | |
| 0.3.5 | 15 / 10 | |
| 0.3.4 | 15 / 10 | |
| 0.3.3 | 15 / 10 | |
| 0.3.2 | 15 / 10 | |
| 0.3.1 | 15 / 10 | |
| 0.3.0 | 15 / 10 | |
| 0.2.2 | 15 / 10 | |
| 0.2.1 | 15 / 10 | |
| 0.2.0 | 15 / 10 | |
| 0.0.1 | 0 / 0 |
v0.31.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.