we are using the Atlaskit npm package @atlaskit/link-datasource. Since version 4.22.1, a new dependency is introduced @atlaskit/afm-i18n-platform-linking-platform-link-datasource. This package references “Atlassian Pty Ltd“ as license, but does not provide any license text. Can you please provide the full license text, or change the license to Apache-2.0 as for most of Atlaskit packages?
Currently updating to @atlaskit/link-datasource version > 4.22.0 is blocked for us due to this license issue.
The team already added a LICENSE.md file stating that the package is licensed under Apache-2.0. It would be nice if they can also update the “license” field in the package.json, such that the license is properly recognized by our tooling as well as npm.
more new Atlassian dependencies showed up referencing “Atlassian Pty Ltd” as license on npmjs. Is this a new policy on your side? It is very inconvenient for us, that we now need to manually check the license file for every new package and new version, whether it references Apache-2.0 or not.
From our side it would be really great, if you could reference Apache-2.0 in the package.json, if this is the license for your package.
Hi @JasonMarx, a change has been pushed, can I ask if the original issue in @atlaskit/afm-i18n-platform-linking-platform-link-datasource has resolved for you?
Regarding the new dependencies - may I ask which packages you are referring to? Or are these all under @atlaskit/link-datasource?
thanks for asking. The issue was kind of resolved. Since a license file was added, we can internally map your license declaration “Atlassian Pty Ltd” to Apache-2.0 for this package. But since we can not be sure, that the license declared in the file will not change or be different in other packages, we can not add a generic mapping.
Is there a reason, why you are using ““Atlassian Pty Ltd” instead of Apache-2.0 in the package.json? This also makes the view on npmjs kind of useless (because nobody adhoc knows what license conditions “Atlassian Pty Ltd” has).
