#cli #search #package

app alpakr-cli

Alpakr CLI 🦙 a package lookup tool for: crates, npm, pypi, and more

2 unstable releases

0.2.3 Apr 21, 2022
0.1.9 Apr 4, 2022
0.1.7 Mar 28, 2022

#2068 in Command line utilities

38 downloads per month

MIT license

138 lines

Alpakr CLI 🦙

A simple package lookup service that isn't too strict about its inputs. Paste a snippet of names and Alpakr will do it's best to provide info about the packages.


Conjugation of 'All' and 'Packager' and pronounced the friendly fury alpaca.

\ ăl-păk′ə \


cargo install alpakr-cli


Copy paste a fragment from a Cargo.toml, package.json or python requirments.txt file and pipe it to alpakr.

$ echo "
console = "0.15.0"
base64 = "0.13.0"
serde = { version = "1.0", features = ["derive"] }" | alpakr

Example output:

console -> A terminal and console abstraction for Rust

base64 -> encodes and decodes base64 as bytes or utf8

serde -> A generic serialization/deserialization framework

Note: for best result paste at least one full line, but more is better.

Other ways to query

$ grep -A 3 "console" Cargo.toml | alpakr
$ alpakr <enter>
console = "0.15.0"
base64 = "0.13.0"
serde = { version = "1.0", features = ["derive"] }
# If you are on Mac use `pbpaste`
$ pbpaste | alpakr


  • --verbose: see encoded payload and full response
  • --json: output as JSON

Supported package managers

  • cargo (crates.io)
  • cargo compiling (crates.io)
  • composer (packagist.org)
  • gem (rubygems.org)
  • gomod (pkg.go.dev)
  • npm (npmjs.com)
  • pip (pypi.org)


In short. I read a lot of code in many different languages. Part of that is looking into what third party packages are used. This can be by reading package.json files or skimming through the text when compiling a Rust program. I wanted to make it easier to learn about packages I don't know about.


~318K SLoC