Expand description
What the dependency’s checkout declares about its distribution.
Every signal is a file in the source tree or its git remote and tags:
a manifest names the package and its version, dist-workspace.toml
says release archives are built, a flake that serves packages
says the repository is a flake input. No registry is asked whether
the version is published; the assessment is offline.
Structs§
- Channel
Evidence - One channel and the evidence behind it.
- Manifest
- What one manifest declares, whatever its format.
- Source
- Everything the offline pass reads from the source.
Enums§
- TagStyle
- Which shape the source’s release tags take.
Functions§
- binstall_
resolves_ to_ github - Whether binstall metadata resolves to this repository’s GitHub releases.
- channels_
of - The channels the evidence supports, in the closed order.
- dist_
hosts_ on_ github - Whether a
dist-workspace.tomlhosts its releases on GitHub:cinamesgithub, andhosting, where set, still names it. A file that does not parse or names another CI is not evidence. - flake_
serves_ package - Whether a flake serves a default package output, judged lexically.
- observe
- Read the source, offline.
- read_
cargo - What a
Cargo.tomldeclares: the package, its bins, its repository. - read_
package_ json - What a
package.jsondeclares: the package, its bins, its repository. - read_
pyproject - What a
pyproject.tomldeclares: the project, its scripts, its repository URL. - tag_
style - The tag shape a tag list shows: the majority form,
Unknownon a tie or an empty list.