vendored | list[vendor.vendoredLibrary] | No | [] | Each library a catalog holds among those the repository declares and those they depend on: unpacked by a plain run, and under --check found and compared with nothing written |
|---|
adapter | vendor.vendoredAdapter | No | | The repo adapter copied into this repository's generated adapter catalog. Absent where the manifest names none, where the catalog is one the repository tracks -- the checkout that develops the adapter -- and where no store answered, which is reported as an error. |
|---|
missing | list[coordinate] | No | [] | Coordinates no catalog this repository reads holds |
|---|
undeclaredRequirements | list[string] | No | [] | Third-party packages a vendored tree needs and this repository does not declare. The half of a closure that cannot be followed: these are installed by a language's own package manager rather than unpacked, so the publisher records what it needed and the consumer is told what it has missed -- instead of meeting it as an ImportError in a tree it only fetched. |
|---|
orphaned | list[string] | No | [] | Directories under the vendor directory that no declared coordinate accounts for. A dependency dropped from the declaration is never visited again, so the tree it left stays -- and stays importable, ahead of this repository's own packages, as a dependency nothing declares. Reported rather than removed: a package may declare a placement a consumer also keeps its own things in, and deciding what in such a directory was ours is the question the .vendored record answers per package rather than per directory. |
|---|
stale | list[string] | No | [] | Coordinates whose unpacked tree is behind what the catalog holds. A vendored tree is a snapshot, and nothing said when the thing it was taken from had moved on -- inside this tree that happens on any edit to a producer, and the stale copy keeps working until the two disagree. Reported by --check, which writes nothing and so has the comparison as its whole answer. |
|---|
behindSource | list[vendor.catalogBehindSource] | No | [] | Catalog entries whose source has moved on since they were built. A copy compared with its catalog cannot see this: a merge that was never rebuilt leaves a catalog every vendored copy matches while all of them are behind, which is how vendor --check passed three retirements over library changes nothing had published. Reported by --check from the source record an archive carries, and only where the directory it names is there to read. |
|---|
requirementsOutOfDate | boolean | No | false | Whether the generated requirements file this repository's language keeps is behind what the fetched trees say they need. The other half of a closure reaches a consumer's package manager as a file the adapter renders and this command writes; under --check nothing is written, so the comparison is the whole answer, and a difference is a repository whose environment would come up short of the source it vendored. |
|---|
unresolvedImports | list[string] | No | [] | Imports a vendored package makes of itself that its unpacked tree does not hold, each as <coordinate>: <file>: <module>. An archive can register, unpack and look well-formed while its package imports a module the archive does not carry, and the import error then arrives in whatever process first imports it -- far from the publish that left the module out. The repo adapter reads the imports, because which statements import and how a module maps to a file are facts about a language. |
|---|
pinnedRepositories | list[string] | No | [] | What each pinned repository's own vendor answered, under the checkout it ran in, when the run was asked to --recurse. Its own output rather than its result, because each is a separate run of this command whose result is that repository's, and a failure among them is an error of this run naming the repository. |
|---|
isComplete | boolean | Yes | | Whether every declared dependency was found and unpacked |
|---|