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
Some tools will look for exact checksums of license files.
More importantly the AGPL starts with this statement:
Everyone is permitted to copy and distribute verbatim copies
of this license document, but changing it is not allowed.
FWIW, I would myself never modify the license text at all as I may violate the AGPL terms, even with the best of intentions and if it were me, I would restore the original text.
$ diff agpl-3.0.txt GNU-AGPL-3.0.txt
0a1>4c5< Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>---> Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>632,633c633,634< <one line to give the program's name and a brief idea of what it does.>< Copyright (C) <year> <name of author>---> PM2 Process manager for Node.JS> Copyright (C) 2013-2016 Strzelewicz Alexandre646c647< along with this program. If not, see <https://www.gnu.org/licenses/>.---> along with this program. If not, see <http://www.gnu.org/licenses/>.661c662,665< <https://www.gnu.org/licenses/>.---> <http://www.gnu.org/licenses/>.>>> --- ALEXANDRE STRZELEWICZ
The text was updated successfully, but these errors were encountered:
While running a routine scan, I found that the AGPL text in this repo has been modified. See the diff below of https://raw.githubusercontent.com/Unitech/pm2/5e708459aca32903fd363230e24c37b3e38bb48d/GNU-AGPL-3.0.txt against https://www.gnu.org/licenses/agpl-3.0.txt ... this may look minor but:
FWIW, I would myself never modify the license text at all as I may violate the AGPL terms, even with the best of intentions and if it were me, I would restore the original text.
The text was updated successfully, but these errors were encountered: