semantic-release/semantic-release

Get semantic-release added as a supported tool for packaging for the OpenSSF Scorecard

Open

#2,779 opened on Apr 28, 2023

View on GitHubContributor guide
 (2 comments) (0 reactions) (0 assignees)JavaScript (1,638 forks)batch import
help wanted

Repository metrics

Stars
 (19,681 stars)
PR merge metrics
 (Avg merge 3h 15m) (33 merged PRs in 30d)

Description

New feature motivation

Since semantic-release is not currently detected as a valid automated workflow packaging tool, projects publishing with it currently receive a low score for the "Packaging" check and also get dinged on the "Token Permissions" check because of the need to grant contents: write

New feature description

No changes to semantic-release itself, but work through the process of getting appropriate details about semantic-release added to the ossf/scorecard project so that semantic-release is recognized as a valid packaging tool for automated workflows.

New feature implementation

contribute semantic-release as a valid tool for packaging following the details found at https://github.com/ossf/scorecard/blob/27cfe92ed356fdb5a398c919ad480817ea907808/docs/checks.md#packaging

this PR added support for python-semantic-release, so it hopefully provides some details for getting the conversation started: https://github.com/ossf/scorecard/pull/1654

Contributor guide

Research direction
Examine the ossf/scorecard project's packaging check configuration and follow the pattern from the python semantic release PR (https://github.com/ossf/scorecard/pull/1654) to add semantic release.
Tech stack
javascript
Domain
devops
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80