Your own packages are not third-party code. They need no license text, and they have no business on a page you show to your customers. When a package is one of yours, open it and use Mark as internal.
What the mark does
- The package is approved and gets the license Internal / proprietary. No license text is needed.
- We never look the package up on a public package source again, so you stop seeing a link to a page that does not exist.
- The package is left out of your public attestation page and of every download you make from it.
- Its name is left out too. The public packages it brings in are still listed, without your package's name beside them.
- It is left out of the license check that warns about one license next to another, so your own code never raises a warning about itself.
- You still see the package in your own inventory, with an Internal badge that says why it is left out.
It is marked once
The mark belongs to the package name, for your whole organization and for every version. Every project and every branch that holds the package follows at once, and the next version of it arrives marked. You do not do this again after each release.
We only ever suggest it
Nothing is marked for you. A package we cannot find where it is published, a package installed straight from a git address, a folder or a link, and a publisher who says the package is not licensed for others all get a suggestion and a button. A typo and one of your own packages look the same from outside, so a person decides. If you marked the wrong one, use Not one of yours. Every row of that name comes back and the package is checked again.