Recent Releases of floss-toolbox
floss-toolbox - Version 2.22.0
What's new
Added
Artifacts
LicensesInventory-tests-assets.zip
To run the tests, you must get the assets attached as artificats to the release you got. For integration tests, get the real_data folder in the integrationtests folder and move it to the same folder in your project. For unit tests, get the data folder in the unittests folder and move it to the same folder in your project. Then you will have to update the configuration values defined in all the config files of the data sets. Indeed, absolute paths are used, so you must look for any "🥜" and replace by the path fragments leading to the folders. After that, run the dry-run.sh script to check wether or not some files are missing. All tests must pass.
LicensesInventory-samples-results.zip
Just some samples of dependencies files and outputs.
floss-toolbox.wiki.zip
The clone of the wiki associated to the release.
- Python
Published by pylapp over 1 year ago
floss-toolbox - Version 2.21.0
What's new
Added
- English template for email text generation about GitHub newcomers
- Bug and feature request templates, and other files for the hygiene of the project
Changed
- [Licenses Inventory] Update to v4.0.6 (#160)
Fixed
- [Diver] Missing execution permission for extract-emails-from-history.sh (#171)
- [Diver] Failed to process repositories at path with whitespaces (#172)
Artifacts
LicensesInventory-tests-assets.zip
To run the tests, you must get the assets attached as artificats to the release you got. For integration tests, get the real_data folder in the integrationtests folder and move it to the same folder in your project. For unit tests, get the data folder in the unittests folder and move it to the same folder in your project. Then you will have to update the configuration values defined in all the config files of the data sets. Indeed, absolute paths are used, so you must look for any "🥜" and replace by the path fragments leading to the folders. After that, run the dry-run.sh script to check wether or not some files are missing. All tests must pass.
LicensesInventory-samples-results.zip
Just some samples of dependencies files and outputs.
floss-toolbox.wiki.zip
The clone of the wiki associated to the release.
- Python
Published by pylapp over 1 year ago
floss-toolbox - Version 2.20.0
What's new
Added
- [Diver] List all contributions by contributors (#153)
Fixed
- [Utils] Fix missing import in configuration.py
Artifacts
LicensesInventory-tests-assets.zip
To run the tests, you must get the assets attached as artificats to the release you got. For integration tests, get the real_data folder in the integrationtests folder and move it to the same folder in your project. For unit tests, get the data folder in the unittests folder and move it to the same folder in your project. Then you will have to update the configuration values defined in all the config files of the data sets. Indeed, absolute paths are used, so you must look for any "🥜" and replace by the path fragments leading to the folders. After that, run the dry-run.sh script to check wether or not some files are missing. All tests must pass.
LicensesInventory-samples-results.zip
Just some samples of dependencies files and outputs.
floss-toolbox.wiki.zip
The clone of the wiki associated to the release.
- Python
Published by pylapp about 2 years ago
floss-toolbox - Version 2.19.0
What's new
Added
- [Diver] Generate CONTRIBUTORS file using Git history (#148)
- [Utils] Apply SPDX headers to sources with REUSE tool (#146)
- [Diver] Check headers of sources files (#101)
Artifacts
LicensesInventory-tests-assets.zip
To run the tests, you must get the assets attached as artificats to the release you got. For integration tests, get the real_data folder in the integrationtests folder and move it to the same folder in your project. For unit tests, get the data folder in the unittests folder and move it to the same folder in your project. Then you will have to update the configuration values defined in all the config files of the data sets. Indeed, absolute paths are used, so you must look for any "🥜" and replace by the path fragments leading to the folders. After that, run the dry-run.sh script to check wether or not some files are missing. All tests must pass.
LicensesInventory-samples-results.zip
Just some samples of dependencies files and outputs.
floss-toolbox.wiki.zip
The clone of the wiki associated to the release.
- Python
Published by pylapp about 2 years ago
floss-toolbox - Version 2.18.0
What's new
Changed
- [Utils] Add licenses names for third-party generator and prompt scripts and new licenses (#141)
- [Utils] Add RSALv2 license in third-party generator scripts (#139)
Artifacts
LicensesInventory-tests-assets.zip
To run the tests, you must get the assets attached as artificats to the release you got. For integration tests, get the real_data folder in the integrationtests folder and move it to the same folder in your project. For unit tests, get the data folder in the unittests folder and move it to the same folder in your project. Then you will have to update the configuration values defined in all the config files of the data sets. Indeed, absolute paths are used, so you must look for any "🥜" and replace by the path fragments leading to the folders. After that, run the dry-run.sh script to check wether or not some files are missing. All tests must pass.
LicensesInventory-samples-results.zip
Just some samples of dependencies files and outputs.
floss-toolbox.wiki.zip
The clone of the wiki associated to the release.
- Python
Published by pylapp about 2 years ago
floss-toolbox - Version 2.17.0
What's new
Added
- [Licenses Inventory] Upgrade to version v4.0.4 (#136)
Changed
- [Licenses Inventory] Update dependency pytests to v8.1.1
- [Utils] Default values for THIRD_PARTY generator script, shared configuration with prompt script
Artifacts
LicensesInventory-tests-assets.zip
To run the tests, you must get the assets attached as artificats to the release you got. For integration tests, get the real_data folder in the integrationtests folder and move it to the same folder in your project. For unit tests, get the data folder in the unittests folder and move it to the same folder in your project. Then you will have to update the configuration values defined in all the config files of the data sets. Indeed, absolute paths are used, so you must look for any "🥜" and replace by the path fragments leading to the folders. After that, run the dry-run.sh script to check wether or not some files are missing. All tests must pass.
LicensesInventory-samples-results.zip
Just some samples of dependencies files and outputs.
floss-toolbox.wiki.zip
The clone of the wiki associated to the release.
- Python
Published by pylapp about 2 years ago
floss-toolbox - Version 2.16.0
What's new
Added
- [Utils] Add metrics and improve outputs for third-party generator scripts
Changed
- [Licenses Inventory] Update dependency pytests to v7.4.4
- [Licenses Inventory] Update dependency beautifulsoup4 to v4.12.3
- [Licenses Inventory] Improve requirements for Python modules in use (#108)
- [Project] Plug Renovate, Gitleaks (#112)
- [Project] Apply REUSE standards (#114)
- [Project] Improve a bit CHANGELOG by leading scope keyword for each line
Security
- [Licenses Inventory] Bump requests from v2.28.1 to v2.31.0 (#3)
Binairies
For integration tests, you must download the archive assets attached in this current release (called "toolbox.LicensesInventory.tests.integrationtests.data.zip"), extract the ZIP folder you got (called toolbox/LicensesInventory/tests/integrationtests/data) and place the data folder in tests/integrationtests folder. Otherwise tests won't work and dry-run script will fail!
- Python
Published by pylapp about 2 years ago
floss-toolbox - Version 2.15.0
Added
- Project - Generate THIRD-PARTY.md based on user inputs (#119)
Binairies
For integration tests, you must download the archive assets attached in this current release (called "toolbox.LicensesInventory.tests.integrationtests.data.zip"), extract the ZIP folder you got (called toolbox/LicensesInventory/tests/integrationtests/data) and place the data folder in tests/integrationtests folder. Otherwise tests won't work and dry-run script will fail!
- Python
Published by pylapp about 2 years ago
floss-toolbox - Version 2.14.0
Added
- Generate template-based text using variables (#84)
Changed
- Make CHANGELOG more compliant (#103)
Binairies
For integration tests, you must download the archive assets attached in this current release (called "toolbox.LicensesInventory.tests.integrationtests.data.zip"), extract the ZIP folder you got (called toolbox/LicensesInventory/tests/integrationtests/data) and place the data folder in tests/integrationtests folder. Otherwise tests won't work and dry-run script will fail!
- Python
Published by pylapp over 2 years ago
floss-toolbox - Version 2.13.0
Features
- #98 Diver - Compute metrics with in parameter URL to clone repo
Bugs
- #96 Project - Broken links in README
Binairies
For integration tests, you must download the archive assets attached in this current release (called "toolbox.LicensesInventory.tests.integrationtests.data.zip", extract the ZIP folder you got called toolbox/LicensesInventory/tests/integrationtests/data and place the data folder in tests/integrationtests folder. Otherwise tests won't work and dry-run script will fail!
- Python
Published by pylapp almost 3 years ago
floss-toolbox - Version 2.12.0
Features
- #28 Diver - Lines of codes and useful metrics
Changes
- #87 Project - Add DCO
- #90 Project - Add security policy file
- #85 Project - Split README files
- #86 Licenses Inventory - Move HTML test files to archives of release
- #93 GitHub - Add in dry-run Gemfiles
Binairies
For integration tests, you must download the archive assets attached in this current release (called "toolbox.LicensesInventory.tests.integrationtests.data.zip", extract the ZIP folder you got called toolbox/LicensesInventory/tests/integrationtests/data and place the data folder in tests/integrationtests folder. Otherwise tests won't work and dry-run script will fail!
- Python
Published by pylapp almost 3 years ago
floss-toolbox - Version 2.11.0
Features
- #82 GitHub - Set teams permissions to read
- Python
Published by pylapp almost 3 years ago
floss-toolbox - Version 2.10.1
Features
- #80 Diver - Path variables not protected
- Python
Published by pylapp about 3 years ago
floss-toolbox - Version 2.10.0
Features
- #77 Licenses Inventory - New release
- Python
Published by pylapp about 3 years ago
floss-toolbox - Version 2.9.0
Features
- #64 Licenses Inventory - New release
- Python
Published by pylapp about 3 years ago
floss-toolbox - Version 2.8.0
Features
- #68 Project - Split dry run
Changes
- Python
Published by pylapp about 3 years ago
floss-toolbox - Version 2.7.0
Features
- #2 Package manager - Extract from files downloaded dependencies #2
- Python
Published by pylapp over 3 years ago
floss-toolbox - Version 2.6.0
Features
- #57 Look for leaks and vulnerabilities with exclusion of projects
- Python
Published by pylapp about 4 years ago
floss-toolbox - Version 2.5.0
Features
Bugs
- #52 Failure of git log if no commits
- Python
Published by pylapp about 4 years ago
floss-toolbox - Version 2.4.0
Features
GitHub
- #44 Look for leaks
Project
- #29 Dry run
Refactoring
GitHub
- #37 Check of vulnerabilities #37
Project
- #40 Fix typo in doc and files
- Python
Published by pylapp about 4 years ago
floss-toolbox - Version 2.3.0
Features
- #20 Find repositories with vulnerabilities (Dependabot)
- Python
Published by pylapp over 4 years ago
floss-toolbox - Version 2.2.0
Features
GitHub
- #19 Backup of repositories
Diver
- #27 Extract email addresses
- Python
Published by pylapp over 4 years ago
floss-toolbox - Version 2.1.0
Features
Diver
- List all contributors of a Git repository using Git history
- Python
Published by pylapp over 4 years ago
floss-toolbox - Version 2.0.0
Features
GitHub
- Get all members of GitHub organization
- Get members who don't have 2FA enabled
- Get members of organization with "company" field undefined
- Get projects which don't have any assigned GitHub team
- Get users which have undefined or hidden email
- Get users which may have not suitable fullname
- Get repositories with undefined licenses
- Get repositories which seems to be unconform (i.e. missing files)
- Get repositories which seems to be empty or have not enough files
- Define permissions (push / write) for all contributors of all projects (except teams and organization owners)
- Define permissions (push / write) for all teams of all projects
- Python
Published by pylapp about 5 years ago