LicenseFinder VS Gitlab CI

Listing the benefits over tools like dependabot and LicenseFinder [1] would help. What does the AI actually do? Summarize dependency changelogs?

One of my projects [2] wraps LicenceFinder in a GitHub action (Ruby only until I merge a pending PR).

[1] https://github.com/pivotal/LicenseFinder

[2] https://github.com/ralexander-phi/license_approval

Obviously that line didn’t fly. What we agreed upon was having a set of license types that were “allowed” and “not allowed”. I know python isn’t as mature in their package management, but you can have something like https://github.com/pivotal/LicenseFinder view the licenses for your configuration.

As an alternative, we've found LincenseFinder, which is an awesome open-source tool to check dependencies for JavaScript. The tool checks the package.json file of a repository and tells you the used licenses. You can also create a list of permitted licenses and LicenseFinder will check if your dependencies are in that list. It basically works very similar as the LicenceChecker for Python did.

## https://github.com/gitlabhq/gitlabhq/issues/694

// https://github.com/gitlabhq/gitlabhq/blob/e6d048d769240760008f0dbb6b811e1ebc675292/app/assets/javascripts/ide/components/repo_tab.vue#L3 import { GlIcon, GlTab } from '@gitlab/ui'; import { mapActions, mapGetters } from 'vuex'; import { __, sprintf } from '~/locale'; import ChangedFileIcon from '~/vue_shared/components/changed_file_icon.vue'; import FileIcon from '~/vue_shared/components/file_icon.vue'; import FileStatusIcon from './repo_file_status_icon.vue'; export default { components: { FileStatusIcon, FileIcon, GlIcon, ChangedFileIcon, GlTab, }, props: { tab: { type: Object, required: true, }, }, data() { return { tabMouseOver: false, }; }, computed: { ...mapGetters(['getUrlForPath']), closeLabel() { if (this.fileHasChanged) { return sprintf(__('%{tabname} changed'), { tabname: this.tab.name }); } return sprintf(__('Close %{tabname}'), { tabname: this.tab.name }); }, showChangedIcon() { if (this.tab.pending) return true; return this.fileHasChanged ? !this.tabMouseOver : false; }, fileHasChanged() { return this.tab.changed || this.tab.tempFile || this.tab.staged || this.tab.deleted; }, }, methods: { ...mapActions(['closeFile', 'updateDelayViewerUpdated', 'openPendingTab']), clickFile(tab) { if (tab.active) return; this.updateDelayViewerUpdated(true); if (tab.pending) { this.openPendingTab({ file: tab, keyPrefix: tab.staged ? 'staged' : 'unstaged' }); } else { this.$router.push(this.getUrlForPath(tab.path)); } }, mouseOverTab() { if (this.fileHasChanged) { this.tabMouseOver = true; } }, mouseOutTab() { if (this.fileHasChanged) { this.tabMouseOver = false; } }, }, };

In setting this up, I have followed the gitlab setup guide and the passenger documentation.

Do you know G2 awards 4.4 stars to both GitLab & CircleCI? Just like GitHub stars, StackShares stack counts reflect the popularity of technology. CircleCI boasts around 7.4k stacks, while GitLab enjoys 31.1k stacks. Besides, GitLab as well as GitLab CI are open-source technologies and have garnered 22k+ stars on GitHub. Wait, this is not a reflection of how good GitLab is at CI/CD. These numbers reflect overall popularity. CircleCI is primarily “a niche-focused continuous integration tool” while GitLab wears multiple hats, including “version control & code collaborator.”