ember
Documentation menuembr 0.13.0

Commands

embr info

Last updated November 3, 2026

embr info <scope>/<name> [--version <req>] [--index <key>]

Shows one package: its newest version, its details, its dependencies, and its recent versions. It only reads, and it works outside a project too.

Output#

mayari/core 0.8.0
An Adaptive Luau Web Backend Framework.

Repository  https://github.com/mayari-org/mayari
Published   2026-10-07 by BizWiz3
Targets     luau

Dependencies
  adpt    mayari/adpt ^
  common  mayari/common ^
  types   mayari/types ^

Versions
  0.8.0  luau
  0.7.8  luau
  0.7.7  luau
  0.7.5  luau
  0.7.4  luau
  0.7.2  luau
  0.7.1  luau
  0.7.0  luau

Add it with `embr add mayari/core`
  • The first line is the name and the version that the details come from.
  • Then the description and a deprecation reason, when the package has them. A deprecated package also names the package to use instead, when its owners gave one.
  • Then each notice of the package, with its id and its range: Warning 3f9c0a1b2c4d for <2.0.0: 1.x leaks memory. embr notices remove takes the id. This needs embr 0.13.0 or later.
  • The details are each field that the index entry has: License, Repository, Homepage, Authors, Published (the date, and the login that published it), Targets, and Requires (the runtime and language versions that the targets need, from [target] requires). An Ember entry has no license or authors. A pesde entry has them.
  • Dependencies and Dev dependencies list each alias with its package and its version requirement, and the index when the entry names one. A pesde peer dependency has (peer).
  • Versions lists the 10 newest versions, newest first, each with its targets. A yanked or deprecated version has a mark. "and N more" counts the rest.
  • The last line is the embr add command, with the --version and --index that you gave.

Behavior#

  • The version is the newest one that is not yanked. --version picks the newest one that the requirement matches, such as --version "^0.7". A yanked version shows only when the requirement matches nothing else, and then the last line says that embr add finds none to install.
  • A prerelease counts only when the package has no stable version, the same rule that an install follows.
  • When a version has more than one target, the details come from the first target. The targets of one version share their dependencies, and Requires joins the requires of each target.
  • Without --index, the package comes from the default index: the default key under [indices], then embr self default-index, then Ember's own index. --index takes a key under [indices], ember, or local. Outside a project, only ember and local are keys. Wally and Forest indices do not list their versions this way, so embr info cannot read them.
  • Indices up to 5 minutes old are used as they are. If the package is not in that copy, Ember refreshes the index once and reads it again.
  • A private or unlisted package is not in the git index. Ember then asks the registry API, with your login or the link key from ember.toml, as an install does.

Examples#

embr info chief/core
embr info chief/core --version "^0.1"
embr info 0x5eal/semver --index pesde

See also#