Signify library vs application

[AlexAxthelm]

It will probably be important to siginify in a repo if its a library or an application, since this impacts expectations on "downstream" (reverse) dependencies.

As an example, it makes sense to enable dependabot alerts to keep dependencies up to date with latest versions for applications, but to have libraries be more conservative in their requirements, since updating a requirement in a lib will require all consumers to also update.

[jdhoffa]

In other contexts (cough 🦀 cough) the distinction is made between a library and an executable/ binary.

In whatever way we choose to make/ identify this distinction, I think it's important that our team/ SPD is aware that anything that can be run is not a library. Something as simple as a script, is something that is expected to be executed, and thus falls more in the "application" territory (even though I'm certain most of our engineers don't think of scripts as applications)