As for now the license is getting published as BSD 3-clause License w/nuclear disclaimer but according to https://spdx.org/licenses/BSD-3-Clause-No-Nuclear-License.html, which I suppose is what you are referring to, the SPDX-identifier would be BSD-3-Clause-No-Nuclear-License.
It would be nice to align it to the SPDX-identifier, because this makes it easier for tools like e.g. Gradle plugins to detect the used license by relying on the SPDX license identifiers.
The published URL to the license is also not correct, as it just references as LICENSE.txt which is not an absolute path to the license file. IMO best would be to link to the official template of the used license, e.g. https://spdx.org/licenses/BSD-3-Clause-No-Nuclear-License.html, so tools can analyze the applied license by looking for an official URL reference.
As for now the license is getting published as
BSD 3-clause License w/nuclear disclaimerbut according to https://spdx.org/licenses/BSD-3-Clause-No-Nuclear-License.html, which I suppose is what you are referring to, the SPDX-identifier would beBSD-3-Clause-No-Nuclear-License.It would be nice to align it to the SPDX-identifier, because this makes it easier for tools like e.g. Gradle plugins to detect the used license by relying on the SPDX license identifiers.
The published URL to the license is also not correct, as it just references as
LICENSE.txtwhich is not an absolute path to the license file. IMO best would be to link to the official template of the used license, e.g. https://spdx.org/licenses/BSD-3-Clause-No-Nuclear-License.html, so tools can analyze the applied license by looking for an official URL reference.