Gatorgrader

Latest version: v1.1.2

Safety actively analyzes 723217 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

1.1.1

Get more info!

Although small, this patch release incorporates changes from three PRs that improve the visibility of information in both GatorGrader output and documentation, as well as formalize the PyPI packaging implementation. Especially important are the `README.md` updates to ensure correctness about the use of Poetry.

What's Changed
* Add metadata for PyPI publishing by Michionlion in https://github.com/GatorEducator/gatorgrader/pull/241
* Update README.md with details/fixes for poetry integration by Michionlion in https://github.com/GatorEducator/gatorgrader/pull/244
* Add expected number of fragments to output by mariakimheinert in https://github.com/GatorEducator/gatorgrader/pull/242


**Full Changelog**: https://github.com/GatorEducator/gatorgrader/compare/v1.1.0...v1.1.1

v1.1.0-legacy
Describe your checks!

Now, the optional `--description` argument allows setting a custom description per check, to cut down on student confusion. In addition, this release includes changes to the release workflow and continuous integration setup.

_Note: This release is the last one compatible with [GatorGradle](https://github.com/GatorEducator/gatorgradle)_
_Note: This release is compatible with Python 3.7+_

What's Changed
* Migration from Travis CI to GitHub Actions by schultzh in https://github.com/GatorEducator/gatorgrader/pull/222
* Document the New Features of GatorGrader in the README by corlettim in https://github.com/GatorEducator/gatorgrader/pull/209
* Add description argument to enable custom check descriptions by Michionlion in https://github.com/GatorEducator/gatorgrader/pull/238

**Full Changelog**: https://github.com/GatorEducator/gatorgrader/compare/v1.0.5...v1.1.0-legacy

1.1.0

_Note: This release should be viewed as **newer** than v1.1.0-legacy_

This release refactors a significant amount of GatorGrader internals, and is the first release available on [PyPI](https://pypi.org/project/gatorgrader/). The release was initially intended to be a stop-gap solution. In future versions, some changes may be made to the structure and distribution of the PyPI package. Additionally, the documentation available in this release may or may not be fully accurate. For users who just wish to use GatorGrader on the command line, all that is needed is to install this package and run `gatorgrader`. For help on syntax and available options, see `gatorgrader --help`.

For users who would like to interact with GatorGrader programmatically, refer to the docstrings available in `gatorgrader.py` and `gator/__init__.py` (or view them in your editor-of-choice with support for a [Python Language Server](https://marketplace.visualstudio.com/items?itemName=ms-python.vscode-pylance)). In summary, however, GatorGrader can be run by importing the `gator` package and calling `gator.grader(["list", "--of", "command", "--line", "arguments"])`, the syntax of which matches previous versions of GatorGrader. For additional help or guidance, see `gatorgrader --help` or reach out to any of the core maintainers.

1.0.5

Fix line endings and formatting and upgrade Travis CI

This PR is a bugfix that resolves issues with incorrect code formatting and the setup with AppVeyor and Travis CI.

corlettim: This PR is to help with fixing the issued line ending error that we have come upon.

gkapfham: This PR includes the following modifications:

- Add a `.gitattributes` file that mandates that line endings follow the Unix standard
- Upgrade the development dependencies listing in the `Pipfile.lock`
- Fix line ending issues that were (likely) causing AppVeyor builds to fail
- Fix AppVeyor configuration so that it uses the supported Python 3.7.5,
which was causing coverage uploads to fail for Python 3.7.4
- Upgrade Travis CI to use the Pro/Com version since Org is now deprecated
- Fix small mistakes in the README file (e.g., trailing blank spaces)

*Auto-generated by [pr-tag-release](https://github.com/Michionlion/pr-tag-release)*

1.0.4

Fix line endings and formatting and upgrade Travis CI

This PR is a bugfix that resolves issues with incorrect code formatting and the setup with AppVeyor and Travis CI.

corlettim: This PR is to help with fixing the issued line ending error that we have come upon.

gkapfham: This PR includes the following modifications:

- Add a `.gitattributes` file that mandates that line endings follow the Unix standard
- Upgrade the development dependencies listing in the `Pipfile.lock`
- Fix line ending issues that were (likely) causing AppVeyor builds to fail
- Fix AppVeyor configuration so that it uses the supported Python 3.7.5,
which was causing coverage uploads to fail for Python 3.7.4
- Upgrade Travis CI to use the Pro/Com version since Org is now deprecated
- Fix small mistakes in the README file (e.g., trailing blank spaces)

*Auto-generated by [pr-tag-release](https://github.com/Michionlion/pr-tag-release)*

1.0.3

Fix line endings and formatting and upgrade Travis CI

This PR is a bugfix that resolves issues with incorrect code formatting and the setup with AppVeyor and Travis CI.

corlettim: This PR is to help with fixing the issued line ending error that we have come upon.

gkapfham: This PR includes the following modifications:

- Add a `.gitattributes` file that mandates that line endings follow the Unix standard
- Upgrade the development dependencies listing in the `Pipfile.lock`
- Fix line ending issues that were (likely) causing AppVeyor builds to fail
- Fix AppVeyor configuration so that it uses the supported Python 3.7.5,
which was causing coverage uploads to fail for Python 3.7.4
- Upgrade Travis CI to use the Pro/Com version since Org is now deprecated
- Fix small mistakes in the README file (e.g., trailing blank spaces)

*Auto-generated by [pr-tag-release](https://github.com/Michionlion/pr-tag-release)*

1.0.2

Fix wording issue for CountCommits check

Updated to say \"The repository has...\" rather than \"Repository has...\" to match other content.

<!-- A short description can be included here -->
<!-- Please ensure that reviewers are assigned -->

What is the current behavior?

Check displays text \"Repository has\" which does not match current format (i.e. it is missing a preceding \"the\" to start the statement). This PR is associated with the below issue:

https://github.com/GatorEducator/gatorgrader/issues/194

What is the new behavior if this PR is merged?
Updated to say \"The repository has...\" to match current format

Other information

This PR has:

- [x] Commit messages that are correctly formatted
- [ ] Tests for newly introduced code
- [ ] Docstrings for newly introduced code

This PR is a small change that fixes 195

<!-- We required the above line statement because GatorGrader uses: -->
<!-- https://github.com/Michionlion/pr-tag-release -->
<!-- to automatically generate a tag and a release from a merged PR -->

Developers
ajciancimino


*Auto-generated by [pr-tag-release](https://github.com/Michionlion/pr-tag-release)*

Page 1 of 3

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.