Skip to main content
SourceTrustSign in

Help center

Guides for SourceTrust: Importing dependencies, reviewing licenses, external obligations, publishing attestation pages, billing, plain-language license explainers, and procurement-oriented explainers for common open-source licenses.

Why did Bulk approve leave this package?

← All articles

Every package that waits for a person says why in plain words. These are the reasons you can meet, what each one means, and what finishes it.

Bulk approve only approves a package when we are sure. We found the license, we confirmed that its text is the standard text, or differs only in ways that ask nothing more of you, and the license is on the list you ticked for Bulk approve. When one of those is missing, the package waits for a person and says why. Open it and the message at the top gives you the reason, what to look at and the steps that finish it. These are the reasons you can meet.

What the colours mean

  • Green: done. Nothing is left on this package.
  • White with a green border: one press left, and nothing to judge.
  • Blue: read this and decide. Nothing we found here asks more of you.
  • Amber: something here changes what you may or must do.
  • Red: a conflict you should not carry into a release.

Nothing is missing

  • Ready for your approval. Everything is in place and the last press is yours. It also reads this way when you changed the license or the text yourself, or when Bulk approve could not confirm the package and you finished it by hand.
  • The license is not on your list for Bulk approve. The package is fine, the license is simply one you asked to see. The message says what that kind of license asks of you. Tick it the next time you press Bulk approve, or add it to your list in the project settings.
  • A person took the approval back. Bulk approve leaves the package until someone approves it again or an import changes its license details.
  • One step is left for your team. The license asks for something you do outside SourceTrust, so the step is yours to do and to tick off.

The license text is not the standard text

  • Only the form of the file is different. A heading over the copyright block, another name or year, a word dropped from a sentence that says the same thing: none of it changes what you may do, so we confirm the text and say nothing about it. Those packages are approved with the rest.
  • A few real things were added, and none of them asks more of you, such as a note on where some code came from. Then the text counts as the standard text and is approved with the rest, and the package shows a short line that something was added, with the words one click away. When an addition points to other license notices, or when several different things were added, the package waits for a person instead, and we quote every place and say what each one does. For several additions we recommend approving the text if you agree. For a line that points to other licenses or notices we do not, because we have not read what it points to: whether that applies to what you deliver is for you to check.
  • A difference adds a condition the standard text does not have. We say so in those words, quote the sentences and say what each one asks of you. If it is a condition you cannot meet, do not approve the package. Replace it, or talk to whoever is responsible for licenses at your company.
  • Some of it is different and we can point at the words. We quote what was added, what is missing and what was changed, so you can go straight to that place in the text. Read it, and approve the text if it does not change what you may do.
  • We found a text and could not confirm it. Read it before you rely on it, then approve it or paste the right one. When we read a text but could not finish checking it, it is in the box for you to read and approve. When the version you use ships no license text at all and we find the unchanged standard text of the license they declared in the publisher's repository, we attach that text and recommend approving it. It is the publisher's own wording, but it is not tied to your exact version, so a person says yes to it. When the repository holds a text that is not exactly the standard one, or the README holds one that reads as the license the publisher names, we offer it for you to read, named for where it came from, and whether it is the license you expect is for you to check.
  • The license is filled in by the publisher. Some licenses name the publisher, a date and what you may not do, and those parts differ from package to package. We never approve one of them for you.
  • A NOTICE or PATENTS file sits next to the license. It can hold credits you must keep, or patent rights it gives or limits. Open the package and read it.

We could not settle which license it is

  • The publisher says one license and the license file says another. The file is what travels with the code, so we show the file's license and recommend it. You choose between the two under License, and Show all licenses lets you pick another one, with a warning that neither of them names it. When you choose a license that is not the file's, the file's text is not used for it. Where that license asks for its text, you add its own text, often its standard text, before you approve. Your public page then says it is the standard text and that the license file has other wording.
  • The only license file we found sits at the top of the source code and not inside the package. It may cover other code as well, so we pick nothing for you and do not offer its text. When the package's own folder holds no text either and we can offer the standard text of the license the publisher states, we offer that text for you to read and approve.
  • The publisher lets you choose between two licenses. The package explains the difference between them and lets you pick either. When one of them clearly asks less of you, we suggest it. When the two cannot be compared that simply, there is no suggestion, and which one fits your use is for you to check. When the package ships no text for one of them, you can pick it only if we can offer its standard text. That text is then used, marked as your choice rather than as something we found in the package.
  • Several licenses apply at the same time, and you have to follow all of them. Each of them needs its own text, and where the package ships none, you can fill it with the standard text of that license in one press when we can offer it. Your public page then says which of the licenses have the standard text.
  • The publisher lists several licenses without saying whether you may choose, or states something too complex for us to settle. Check the project's own page for how it is licensed, then choose.
  • The license file is the publisher's own terms, or a license we do not have in our library yet. Read it, choose the license that fits or Other license, and approve only if your use is allowed.
  • The file we found is not a license text at all. Find the license on the package's page and paste it.

There is no text

  • The publisher states a license and this version comes without a text. When the source code holds a text that is not the standard one, or the README holds one that reads as that license, we offer it for you to read. When we find none and we can offer the standard text of that license, we offer it: check for yourselves for good measure, then approve it, and your public page says it is the standard text. Where the license asks for no text, you can press Accept the license without a text. Where it asks for its text and we cannot offer the standard text, you tick that you understand the package will have none first. The package then has no license text to pass on, and we record that no text was published. Or paste the text you agreed to.
  • We found no license at all. Without a license you have no stated right to use the package. Look for one on the package's page for this version and in its source code, or think about replacing it.
  • The license needs its text, and none is saved for the package yet. You must be able to show the text to the people you pass the package on to, so look for it on the package's page for this version and in its source code, and paste it.

It is one of your own

  • We could not find this version where it is published, and it looks like one of yours. If it is, mark it as internal and we remember that for your whole organization.
  • The package was not installed from the public package source. It comes straight from a git address, a folder or a link, and we never swap it for a package with the same name somewhere else.
  • The publisher marks the package as not licensed for others. That is normal for a company's own packages. If it belongs to someone else, you need their permission.

We could not check it

Sometimes the check itself does not get through: we tried and could not get the package or its text, the copy we got was not the one your project recorded, we could not read all of the package, there is no fixed version to check, we could not find this exact version where it is published, or we could not read all of its license files. We never turn that into a judgement about the package, and we never say it has no text. The page says we could not finish and shows the way on: the package's page, its source code, or your installed copy. When only the answer was slow, we check the package again on our own and tell you that we are doing it. When you press Check again yourselves, you get an answer within a minute: the text, or a plain message that we could not get it. When we read the text but could not finish checking it, the text is there for you to read and approve.

A package you open while the import is still running says that we are still checking it. Nothing is wrong. Review other packages meanwhile, and come back when the check has finished.
See Help center → Reviewing a package (Reviewing a package), Bulk approve (Bulk approve), and Auto-fetch license text (Auto-fetch license text).