sigit/sigit.io
7
2
Fork 0
Code Issues 32 Pull Requests 2 Actions Packages Projects 1 Releases Wiki Activity

licence + vulnerability check #90

New Issue
Closed
opened 2024-05-28 21:44:30 +00:00 by b · 1 comment
b commented 2024-05-28 21:44:30 +00:00
Owner
Copy Link

As part of the pipeline (to staging) we should check licences that they are in the following whitelist:

'AFLv2.1;Apache 2.0;Apache-2.0;Apache*;Artistic-2.0;0BSD;BSD*;BSD-2-Clause;BSD-3-Clause;CC0-1.0;CC-BY-3.0;CC-BY-4.0;ISC;MIT;MPL-2.0;ODC-By-1.0;Python-2.0;Unlicense;'

We should also check that npm audit reports 0 vulnerabilities. If there is a strong argument, we could change this to npm audit --omit=dev --audit-level=low.

As part of the pipeline (to staging) we should check licences that they are in the following whitelist: ` 'AFLv2.1;Apache 2.0;Apache-2.0;Apache*;Artistic-2.0;0BSD;BSD*;BSD-2-Clause;BSD-3-Clause;CC0-1.0;CC-BY-3.0;CC-BY-4.0;ISC;MIT;MPL-2.0;ODC-By-1.0;Python-2.0;Unlicense;'` We should also check that `npm audit` reports 0 vulnerabilities. If there is a strong argument, we could change this to `npm audit --omit=dev --audit-level=low`.
👍 1
s commented 2024-05-29 04:58:39 +00:00
Owner
Copy Link

linked to #38

linked to #38
y added the
Priority
Medium
 label 2024-06-25 13:34:17 +00:00
y added
Priority
High
 and removed
Priority
Medium
 labels 2024-06-25 13:35:25 +00:00
y self-assigned this 2024-06-25 13:35:34 +00:00
enes closed this issue 2024-08-07 13:54:36 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Kind/Breaking
Breaking change that won't be backward compatible
Kind/Bug
Something is not working
Kind/Documentation
Documentation changes
Kind/Enhancement
Improve existing functionality
Kind/Feature
New functionality
Kind/Security
This is security issue
Kind/Testing
Issue or pull request related to testing
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
No Label
Priority
High
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees y
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sigit/sigit.io#90
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?