External services · rule
package.licence_not_allowed
Proprietary package isn't installed from git.
Area 11, External services; not declinable; the next step is usually the human's.
Only a package installed from git may be proprietary:
// Generated by Jadpo from the installed packages; update it with `jadpo package add`, `update` or `remove`, never by hand.record lock 1package Postcodes.v2 version 2.1.0 path ../postcodes digest sha256:3fcf79f4803b01a5f2f4a9ff6550c4ee20fe3a4e93e608faa0c447eabf6a3191
error: Package `Postcodes.v2` is proprietary but wasn't installed from git --> packages/postcodes/v2/package.jadpo:3:5 |3 | licence: Licence.proprietary | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^ proprietary reason: Only a package installed from git, a company's private package, may be `Licence.proprietary`; the registry and other sources carry packages others may use. next: Install the package from its git repository, or publish it under one of the open licences (human) rule: package.licence_not_allowed help: https://jadpo.dev/docs/errors/package.licence_not_allowedcheck failed: 1 error, 2 files
Markdown for agents: /docs/errors/package.licence_not_allowed.md.Built from Jadpo main at a707efb.