[ protorip ]
---
site: protos.rip
page: compatibility
---
                                    __ 
  _________  ____ ___  ____  ____ _/ /_
 / ___/ __ \/ __ `__ \/ __ \/ __ `/ __/
/ /__/ /_/ / / / / / / /_/ / /_/ / /_  
\___/\____/_/ /_/ /_/ .___/\__,_/\__/  
                   /_/                 
# buf cli compatibility
works with buf cli >= v1.67.0.
unfamiliar with buf cli? check out the [official docs](https://buf.build/docs/cli/) first.
## what works
### dependencies
resolve, lock, and build against remote dependencies.
```yaml
deps:
- protos.rip/acme/petapis
```
```bash
buf dep update
buf dep graph
buf build
buf generate
```
### auth
sign in via browser or [api key](/dashboard) to publish modules or access private modules.
```bash
buf registry login protos.rip
buf registry whoami
```
### publishing
push modules and tag them with labels.
```bash
buf push
buf push --label v1.0.0
```
### module and label management
full management of modules, labels, and commits.
```bash
buf registry module create / info / list / update / delete
buf registry label create / info / list / archive / unarchive
buf registry commit list / info
```
## not supported
remote code generation (`buf generate` with remote plugins) — not supported. use local plugins instead.
alpha/beta CLI features: `buf alpha registry token` (use the dashboard for API keys), `buf beta registry webhook`, `buf registry sdk info`.
cross-registry dependencies: buf has experimental cross-registry federation but relies on a hardcoded allowlist that does not include protos.rip. ensure all modules in your dependency chain are published to protos.rip. we maintain a handful of well-known [curated mirrors](/registry) that should meet most needs.
## compatibility target
protos.rip implements [`bufbuild/registry-proto`](https://github.com/bufbuild/registry-proto) (the BSR protocol) v1 stable services. some other non-stable services are provided for buf cli compatibility.
last tested with buf cli v1.67.0 (april 2026).