| Age | Commit message (Collapse) | Author |
|
* docs: Add changelog entry
* fix: update spec to match expected behaviour
|
|
|
|
|
|
* Install ca-certificates-mono
* Download *.deb files to /opt/toolcache/mono
|
|
* Install custom ca certificate in location where nuget can recognize it
* Add subject alternative name to the generate x509 cert
* Do not cache packages and https requests
* Detect vbproj, fsproj, csproj, and sln files
* Improve nuget package detection
* Parse SPDX license expression from nuspec files
* Update version and update CHANGELOG
|
|
|
|
* Update CHANGELOG and fix typo
* Render severity based on exit code
* Explicitly specify the default GOPROXY
* Default to -mod=readonly and allow override
* Do not modify `vendor` directory if it exists.
* Skip `go mod tidy` to prevent modifying projects files.
* Include dependencies that appear in go.mod but are not present in the
vendor directory.
* Remove severity from log output
* Wipe golang module cache before each spec
```plaintext
The -mod build flag provides additional control over updating and use of
go.mod.
If invoked with -mod=readonly, the go command is disallowed from the
implicit automatic updating of go.mod described above. Instead, it fails
when any changes to go.mod are needed. This setting is most useful to
check that go.mod does not need updates, such as in a continuous
integration and testing system. The "go get" command remains permitted
to update go.mod even with -mod=readonly, and the "go mod" commands do
not take the -mod flag (or any other build flags).
If invoked with -mod=vendor, the go command loads packages from the main
module's vendor directory instead of downloading modules to and loading
packages from the module cache. The go command assumes the vendor
directory holds correct copies of dependencies, and it does not compute
the set of required module versions from go.mod files. However, the go
command does check that vendor/modules.txt (generated by 'go mod
vendor') contains metadata consistent with go.mod.
If invoked with -mod=mod, the go command loads modules from the module
cache even if there is a vendor directory present.
If the go command is not invoked with a -mod flag and the vendor
directory is present and the "go" version in go.mod is 1.14 or higher,
the go command will act as if it were invoked with -mod=vendor.
```
- https://golang.org/cmd/go/#hdr-Maintaining_module_requirements
|
|
* Inline creation of PipPackage in legacy scan results
* Add CHANGELOG entry
|
|
|
|
* Install certificate in root ca trust store
* Use PIP_CERT environment variable to specify path to the certificate bundle
* Do not override user provided PIP_CERT
* Perform shallow clone when possible
* Update CHANGELOG and bump version
|
|
* Add CHANGELOG entry and bump version
* Change default log level to `warn`
* Log stderr output if exit status is not successful
|
|
* Exclude dependencies in "develop" group"
* Install pipenv by default
* Use .venv to match the default location as pipenv
* Use pip-licenses to detect licenses in Pipfile project
* Add variation of the MIT License
* Redirect asdf install stdout to /dev/null
* Add CHANGELOG entry and bump version
|
|
* Add PIL License to list of normalized licenses
* Update Python 3 v2.0 report fixture
* Add CHANGELOG entry
* Define local variables in bash functions
* Ensure `SETUP_CMD` continues to work for python projects
* build virtualenv app-data cache
* Fallback to legacy scanner when SETUP_CMD is used
* Extract Shell class to be able to pass custom env
|
|
* Read PIP_INDEX_URL to identify where to download packages from
|
|
* Install packages when multiple maven modules are detected
* Add CHANGELOG entry
* Install gem silently
* Add package manager to test description
* Sort paths
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* Details can be found [here](https://gitlab.com/gitlab-org/gitlab/issues/13748#note_235810786)
|
|
|
|
https://gitlab.com/gitlab-org/security-products/license-management/merge_requests/50
|
|
|