You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Up to an including v0.13.0 the licence on pypi was correct with reference to the repo itself, i.e. MIT Licence. However from v0.14.0 onwards this is not the case. This can be seen if you inspect the releases page for v0.13.0 on pypi as compared to v0.14.0. This is probably something really simple but if it could be resolved that would be brilliant because this is causing deptry to flag as unlicensed in security tooling.
Thanks for your report! It looks like Poetry sets that automatically, so we lost that information when switching over PDM. Will add the classifier manually.
@mkniewallner thanks for being so responsive! I really love deptry so I’m glad I can now use it without tripping our security tooling. Thanks again for acting so quickly!
Describe the bug
Up to an including v0.13.0 the licence on
pypi
was correct with reference to the repo itself, i.e. MIT Licence. However from v0.14.0 onwards this is not the case. This can be seen if you inspect the releases page for v0.13.0 onpypi
as compared to v0.14.0. This is probably something really simple but if it could be resolved that would be brilliant because this is causingdeptry
to flag as unlicensed in security tooling.To Reproduce
Steps to reproduce the behavior:
License: MIT License (MIT)
Expected behavior
The licence listing would continue between versions as it has not changed.
Additional context
Thank you so much for making a tool like
deptry
that is so cool and useful, I hope this can be fixed quickly :)The text was updated successfully, but these errors were encountered: