Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps): bump the npm_and_yarn group across 1 directory with 2 updates #226

Merged
merged 2 commits into from
Jan 28, 2025

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 28, 2025

Bumps the npm_and_yarn group with 2 updates in the / directory: cross-spawn and micromatch.

Updates cross-spawn from 7.0.3 to 7.0.6

Changelog

Sourced from cross-spawn's changelog.

7.0.6 (2024-11-18)

Bug Fixes

  • update cross-spawn version to 7.0.5 in package-lock.json (f700743)

7.0.5 (2024-11-07)

Bug Fixes

  • fix escaping bug introduced by backtracking (640d391)

7.0.4 (2024-11-07)

Bug Fixes

Commits
  • 77cd97f chore(release): 7.0.6
  • 6717de4 chore: upgrade standard-version
  • f700743 fix: update cross-spawn version to 7.0.5 in package-lock.json
  • 9a7e3b2 chore: fix build status badge
  • 0852683 chore(release): 7.0.5
  • 640d391 fix: fix escaping bug introduced by backtracking
  • bff0c87 chore: remove codecov
  • a7c6abc chore: replace travis with github workflows
  • 9b9246e chore(release): 7.0.4
  • 5ff3a07 fix: disable regexp backtracking (#160)
  • Additional commits viewable in compare view

Updates micromatch from 4.0.7 to 4.0.8

Release notes

Sourced from micromatch's releases.

4.0.8

Ultimate release that fixes both CVE-2024-4067 and CVE-2024-4068. We consider the issues low-priority, so even if you see automated scanners saying otherwise, don't be scared.

Changelog

Sourced from micromatch's changelog.

[4.0.8] - 2024-08-22

Commits

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
  • @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
  • @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
  • @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
  • @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions
    You can disable automated security fix PRs for this repo from the Security Alerts page.

…dates

Bumps the npm_and_yarn group with 2 updates in the / directory: [cross-spawn](https://github.com/moxystudio/node-cross-spawn) and [micromatch](https://github.com/micromatch/micromatch).


Updates `cross-spawn` from 7.0.3 to 7.0.6
- [Changelog](https://github.com/moxystudio/node-cross-spawn/blob/master/CHANGELOG.md)
- [Commits](moxystudio/node-cross-spawn@v7.0.3...v7.0.6)

Updates `micromatch` from 4.0.7 to 4.0.8
- [Release notes](https://github.com/micromatch/micromatch/releases)
- [Changelog](https://github.com/micromatch/micromatch/blob/master/CHANGELOG.md)
- [Commits](micromatch/micromatch@4.0.7...4.0.8)

---
updated-dependencies:
- dependency-name: cross-spawn
  dependency-type: indirect
  dependency-group: npm_and_yarn
- dependency-name: micromatch
  dependency-type: indirect
  dependency-group: npm_and_yarn
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot requested a review from jmuelbert as a code owner January 28, 2025 09:20
@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Jan 28, 2025
Copy link

trunk-io bot commented Jan 28, 2025

Merging to main in this repository is managed by Trunk.

  • To merge this pull request, check the box to the left or comment /trunk merge below.

Copy link

github-actions bot commented Jan 28, 2025

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

OpenSSF Scorecard

PackageVersionScoreDetails
npm/cross-spawn 7.0.6 🟢 3.8
Details
CheckScoreReason
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Packaging⚠️ -1packaging workflow not detected
Code-Review⚠️ 2Found 8/29 approved changesets -- score normalized to 2
Maintained🟢 1013 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts🟢 10no binaries found in the repo
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Pinned-Dependencies🟢 3dependency not pinned by hash detected -- score normalized to 3
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Security-Policy⚠️ 0security policy file not detected
License🟢 10license file detected
Fuzzing⚠️ 0project is not fuzzed
Signed-Releases⚠️ -1no releases found
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0
Vulnerabilities⚠️ 044 existing vulnerabilities detected
npm/micromatch 4.0.8 🟢 4.2
Details
CheckScoreReason
Binary-Artifacts🟢 10no binaries found in the repo
Dangerous-Workflow🟢 10no dangerous workflow patterns detected
Maintained⚠️ 00 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 0
Packaging⚠️ -1packaging workflow not detected
Code-Review⚠️ 2Found 5/20 approved changesets -- score normalized to 2
Token-Permissions⚠️ 0detected GitHub workflow tokens with excessive permissions
Pinned-Dependencies⚠️ 0dependency not pinned by hash detected -- score normalized to 0
CII-Best-Practices⚠️ 0no effort to earn an OpenSSF best practices badge detected
Vulnerabilities🟢 100 existing vulnerabilities detected
License🟢 10license file detected
Fuzzing⚠️ 0project is not fuzzed
Signed-Releases⚠️ -1no releases found
Security-Policy🟢 10security policy file detected
Branch-Protection⚠️ 0branch protection not enabled on development/release branches
SAST⚠️ 0SAST tool is not run on all commits -- score normalized to 0

Scanned Files

  • pnpm-lock.yaml

Copy link

github-actions bot commented Jan 28, 2025

Here are some friendly prose warnings from write-good:

In ./SECURITY.md
=============
 the moment checkconnect only considers the very latest commit to be
                         ^^^^
"only" can weaken meaning on line 5 at column 27
-------------
nnect only considers the very latest commit to be
                         ^^^^
"very" is a weasel word and can weaken meaning on line 5 at column 46
-------------
he very latest commit to be
                         ^^^^^^^^^^^^
"be
supported" may be passive voice on line 5 at column 68
-------------
automated updates to minimize the time between vulnerability publication
                     ^^^^^^^^
"minimize" is wordy or unneeded on line 7 at column 21
-------------
In the near future we will introduce versioning, so expect this section to
^^^^^^^^^^^^^^^^^^
"In the near future" is wordy or unneeded on line 15 at column 0


In ./AUTHORS.md
=============
or without modification, are
                         ^^^^^^^^^^^^^
"are
permitted" may be passive voice on line 7 at column 69
-------------
this notice are preserved.
            ^^^^^^^^^^^^^
"are preserved" may be passive voice on line 9 at column 12


In ./CHANGELOG.md
=============
ges to this project will be documented in this file.
                         ^^^^^^^^^^^^^
"be documented" may be passive voice on line 3 at column 41
-------------
The format is based on
           ^^^^^^^^
"is based" may be passive voice on line 5 at column 11


In ./.github/CODE_OF_CONDUCT.md
=============
- Giving and gracefully accepting constructive feedback
             ^^^^^^^^^^
"gracefully" can weaken meaning on line 22 at column 13
-------------
sing on what is best not just for us as individuals, but for the
                         ^^^^
"just" can weaken meaning on line 25 at column 31
-------------
  overall community
  ^^^^^^^
"overall" is wordy or unneeded on line 26 at column 2
-------------
t which could reasonably be considered inappropriate in a
                         ^^^^^^^^^^^^^
"be considered" may be passive voice on line 37 at column 39
-------------
nacceptable behavior may be
                         ^^^^^^^^^^^
"be
reported" may be passive voice on line 62 at column 72
-------------
il]. All complaints will be reviewed and
                         ^^^^^^^^^^^
"be reviewed" may be passive voice on line 64 at column 51
-------------
investigated promptly and fairly.
             ^^^^^^^^
"promptly" can weaken meaning on line 65 at column 13
-------------
nvestigated promptly and fairly.
                         ^^^^^^
"fairly" is a weasel word and can weaken meaning on line 65 at column 26
-------------
All community leaders are obligated to respect the privacy and security of
                      ^^^^^^^^^^^^^
"are obligated" may be passive voice on line 67 at column 22
-------------
te. A public apology may be requested.
                         ^^^^^^^^^^^^
"be requested" may be passive voice on line 83 at column 57
-------------
ing the Code of Conduct, is allowed during
                         ^^^^^^^^^^
"is allowed" may be passive voice on line 105 at column 54
-------------
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
                     ^^^^^^^^^^
"is adapted" may be passive voice on line 120 at column 21
-------------
munity Impact Guidelines were inspired by
                         ^^^^^^^^^^^^^
"were inspired" may be passive voice on line 124 at column 28


In ./.github/PULL_REQUEST_TEMPLATE.md
=============
s one or more issues, or is related to
                         ^^^^^^^^^^
"is related" may be passive voice on line 11 at column 55
-------------
## How Has This Been Tested?
                ^^^^^^^^^^^
"Been Tested" may be passive voice on line 21 at column 16
-------------
request before all these are done, but
                         ^^^^^^^^
"are done" may be passive voice on line 32 at column 51
-------------
     they should be done before getting merged. -->
                 ^^^^^^^
"be done" may be passive voice on line 33 at column 17
-------------
 If the key of a setting is changed, the 'old' attribute is updated or
                         ^^^^^^^^^^
"is changed" may be passive voice on line 35 at column 30
-------------
ged, the 'old' attribute is updated or
                         ^^^^^^^^^^
"is updated" may be passive voice on line 35 at column 62
-------------
      it is resolved in SettingsUpdater.
      ^^^^^
"it is" is wordy or unneeded on line 36 at column 6
-------------
      it is resolved in SettingsUpdater.
         ^^^^^^^^^^^
"is resolved" may be passive voice on line 36 at column 9
-------------
hanges are notable, they are documented in
                         ^^^^^^^^^^^^^^
"are documented" may be passive voice on line 39 at column 41
-------------
## Additional text
   ^^^^^^^^^^
"Additional" is wordy or unneeded on line 42 at column 3
-------------
the translations need to be updated. --->
                         ^^^^^^^^^^
"be updated" may be passive voice on line 45 at column 45


In ./.github/CONTRIBUTING.md
=============
checkconnect is a large project and contributions are more than welcome, so
^^^^^^^^^^^^
"checkconnect" is repeated on line 3 at column 0
-------------
Submit only relevant commits. We don't mind many commits in a pull request,
       ^^^^
"only" can weaken meaning on line 10 at column 7
-------------
t commits. We don't mind many commits in a pull request,
                         ^^^^
"many" is a weasel word and can weaken meaning on line 10 at column 44
-------------
 The pull request should be created from a
                         ^^^^^^^^^^
"be created" may be passive voice on line 13 at column 51
-------------
commits that changes too many
                         ^^^^
"many" can weaken meaning on line 36 at column 68
-------------
  things at the same time are very hard to review. Split large commits into
  ^^^^^^
"things" can weaken meaning on line 37 at column 2
-------------
ngs at the same time are very hard to review. Split large commits into
                         ^^^^
"very" is a weasel word and can weaken meaning on line 37 at column 30
-------------
  passes. Tests can be run using the command
                    ^^^^^^
"be run" may be passive voice on line 42 at column 20
-------------
Especially if you modify something existing, be very clear! Have you
^^^^^^^^^^
"Especially" can weaken meaning on line 55 at column 0
-------------
Especially if you modify something existing, be very clear! Have you
                  ^^^^^^
"modify" is wordy or unneeded on line 55 at column 18
-------------
y something existing, be very clear! Have you
                         ^^^^
"very" is a weasel word and can weaken meaning on line 55 at column 48
-------------
y algorithms, or did you just intend to reorder the code? Justify
                         ^^^^
"just" can weaken meaning on line 56 at column 35
-------------
why the changes are needed.
                ^^^^^^^^^^
"are needed" may be passive voice on line 57 at column 16
-------------
are things we want help with.
    ^^^^^^
"things" can weaken meaning on line 91 at column 4
-------------
git merge --ff-only upstream/dev
               ^^^^
"only" can weaken meaning on line 111 at column 15
-------------
ch and that it's created off of _dev_. Tip: Give it a descriptive
                         ^^^^^^
"off of" is wordy or unneeded on line 119 at column 35
-------------
  'implement-lengthframeencoder-323' or '295-implement-recvbuffer', so that
   ^^^^^^^^^
"implement" is wordy or unneeded on line 121 at column 3
-------------
  others can see what is being worked on.
                         ^^^^^^^^^^^^
"being worked" may be passive voice on line 122 at column 25
-------------
away in your branch it's quite possible that your
                         ^^^^^
"quite" is a weasel word on line 148 at column 46
-------------
upstream _dev_ may be updated. If this happens you should:
                   ^^^^^^^^^^
"be updated" may be passive voice on line 149 at column 19
-------------
git merge --ff-only upstream/dev
               ^^^^
"only" can weaken meaning on line 163 at column 15
-------------
up with several "messy" merges in your history, which we don't want. This
        ^^^^^^^
"several" is a weasel word on line 179 at column 8
-------------
quite often, rather than run the risk of potential merge issues further
^^^^^
"quite" is a weasel word on line 184 at column 0
-------------
just commit to your local branch and push the branch just like you did the
^^^^
"just" can weaken meaning on line 190 at column 0
-------------
anch and push the branch just like you did the
                         ^^^^
"just" can weaken meaning on line 190 at column 53
-------------
ommit will automatically be included in the Pull request.
                         ^^^^^^^^^^^
"be included" may be passive voice on line 191 at column 43
-------------
 can create a new branch off of _develop_ and then cherry pick the
                         ^^^^^^
"off of" is wordy or unneeded on line 215 at column 31


In ./docs/about/EUPL-1.2.md
=============
defined below) which is provided under the terms of this Licence. Any use
                     ^^^^^^^^^^^
"is provided" may be passive voice on line 6 at column 21
-------------
rised under this Licence is prohibited (to
                         ^^^^^^^^^^^^^
"is prohibited" may be passive voice on line 7 at column 57
-------------
the extent such use is covered by a right of the copyright holder of the
                    ^^^^^^^^^^
"is covered" may be passive voice on line 8 at column 20
-------------
Work). The Work is provided under the terms of this Licence when the
                ^^^^^^^^^^^
"is provided" may be passive voice on line 9 at column 16
-------------
ced the following notice immediately
                         ^^^^^^^^^^^
"immediately" can weaken meaning on line 10 at column 60
-------------
s or software that could be created by the
                         ^^^^^^^^^^
"be created" may be passive voice on line 22 at column 54
-------------
  Original Work required in order to classify a work as a Derivative Work;
                         ^^^^^^^^^^^
"in order to" is wordy or unneeded on line 25 at column 25
-------------
  this extent is determined by copyright law applicable in the country
              ^^^^^^^^^^^^^
"is determined" may be passive voice on line 26 at column 14
-------------
 for people to study and modify.
                         ^^^^^^
"modify" is wordy or unneeded on line 30 at column 37
-------------
code which has generally been compiled and
                         ^^^^^^^^^^^^^
"been compiled" may be passive voice on line 31 at column 53
-------------
  which is meant to be interpreted by a computer as a program.
        ^^^^^^^^
"is meant" may be passive voice on line 32 at column 8
-------------
  which is meant to be interpreted by a computer as a program.
                    ^^^^^^^^^^^^^^
"be interpreted" may be passive voice on line 32 at column 20
-------------
nce to do the following, for the duration of copyright
                         ^^^^^^^^^^^^^^^^^^^
"for the duration of" is wordy or unneeded on line 49 at column 43
-------------
- modify the Work, and make Derivative Works based upon the Work,
  ^^^^^^
"modify" is wordy or unneeded on line 54 at column 2
-------------
Those rights can be exercised on any media, supports and formats, whether
                 ^^^^^^^^^^^^
"be exercised" may be passive voice on line 62 at column 17
-------------
he extent allowed by law in order to make
                         ^^^^^^^^^^^
"in order to" is wordy or unneeded on line 65 at column 54
-------------
utable Code. If the Work is provided as Executable Code, the Licensor
                         ^^^^^^^^^^^
"is provided" may be passive voice on line 74 at column 29
-------------
provides in addition a machine-readable copy of the Source Code of the Work
         ^^^^^^^^^^^
"in addition" is wordy or unneeded on line 75 at column 9
-------------
where the Source Code is easily and freely accessible for as
                         ^^^^^^
"easily" can weaken meaning on line 78 at column 38
-------------
Nothing in this Licence is intended to deprive the Licensee of the benefits
                        ^^^^^^^^^^^
"is intended" may be passive voice on line 83 at column 24
-------------
on right:** The Licensee shall keep intact all copyright, patent
                         ^^^^^
"shall" is wordy or unneeded on line 93 at column 36
-------------
tating that the Work has been modified and the date of
                         ^^^^^^^^^^^^^
"been modified" may be passive voice on line 98 at column 44
-------------
will be done under the terms of this Licence or of a later version of this
     ^^^^^^^
"be done" may be passive voice on line 103 at column 5
-------------
is expressly distributed only under this
                         ^^^^
"only" can weaken meaning on line 104 at column 58
-------------
mmunicating ‘EUPL v. 1.2 only’.
                         ^^^^
"only" can weaken meaning on line 105 at column 67
-------------
nnot offer or impose any additional
                         ^^^^^^^^^^
"additional" is wordy or unneeded on line 106 at column 60
-------------
Communication can be done under the terms of this Compatible Licence. For
                  ^^^^^^^
"be done" may be passive voice on line 113 at column 18
-------------
f the Compatible Licence shall prevail.
                         ^^^^^
"shall" is wordy or unneeded on line 117 at column 51
-------------
Code or indicate a repository where this Source will be easily and freely
        ^^^^^^^^
"indicate" is wordy or unneeded on line 121 at column 8
-------------
here this Source will be easily and freely
                         ^^^^^^
"easily" can weaken meaning on line 121 at column 56
-------------
granted hereunder is owned by him/her or licensed to him/her and that
                  ^^^^^^^^
"is owned" may be passive voice on line 133 at column 18
-------------
are owned by him/her or licensed to him/her and that he/she has the power
^^^^^^^^^
"are owned" may be passive voice on line 136 at column 0
-------------
original Licensor and subsequent Contributors grant You a licence to their
                      ^^^^^^^^^^
"subsequent" is wordy or unneeded on line 138 at column 22
-------------
continuously improved by numerous
                         ^^^^^^^^
"numerous" is wordy or unneeded on line 143 at column 66
-------------
Contributors. It is not a finished work and may therefore contain defects
              ^^^^^
"It is" is wordy or unneeded on line 144 at column 14
-------------
 a finished work and may therefore contain defects
                         ^^^^^^^^^
"therefore" is wordy or unneeded on line 144 at column 48
-------------
 ‘bugs’ inherent to this type of development. For the above reason, the
                         ^^^^^^^
"type of" is wordy or unneeded on line 145 at column 27
-------------
Work is provided under the Licence on an ‘as is’ basis and without
     ^^^^^^^^^^^
"is provided" may be passive voice on line 146 at column 5
-------------
warranties of any kind concerning the Work, including without limitation
                       ^^^^^^^^^^
"concerning" is wordy or unneeded on line 147 at column 23
-------------
even if the Licensor has been advised of
                         ^^^^^^^^^^^^
"been advised" may be passive voice on line 161 at column 59
-------------
sibility of such damage. However, the Licensor will be liable under
                         ^^^^^^^
"However" is wordy or unneeded on line 162 at column 32
-------------
## 9.Additional agreements
     ^^^^^^^^^^
"Additional" is wordy or unneeded on line 165 at column 5
-------------
ay choose to conclude an additional
                         ^^^^^^^^^^
"additional" is wordy or unneeded on line 167 at column 59
-------------
However, if accepting obligations, You may act only on your own behalf and
^^^^^^^
"However" is wordy or unneeded on line 169 at column 0
-------------
obligations, You may act only on your own behalf and
                         ^^^^
"only" can weaken meaning on line 169 at column 47
-------------
other Contributor, and only if You agree to indemnify, defend, and hold
                       ^^^^
"only" can weaken meaning on line 171 at column 23
-------------
additional liability.
^^^^^^^^^^
"additional" is wordy or unneeded on line 174 at column 0
-------------
ions of this Licence can be accepted by clicking on an icon ‘I
                         ^^^^^^^^^^^
"be accepted" may be passive voice on line 178 at column 35
-------------
n any other similar way, in accordance
                         ^^^^^^^^^^^^^^^^^^
"in accordance
with" is wordy or unneeded on line 180 at column 58
-------------
ance of this Licence and all of its terms and
                         ^^^^^^
"all of" is wordy or unneeded on line 182 at column 53
-------------
 accept this Licence and all of its
                         ^^^^^^
"all of" is wordy or unneeded on line 183 at column 63
-------------
ommunication of the Work by means of
                         ^^^^^^^^^^^
"by means of" is wordy or unneeded on line 191 at column 57
-------------
ed by the applicable law regarding the Licensor, the Licence and the
                         ^^^^^^^^^
"regarding" is wordy or unneeded on line 195 at column 32
-------------
s granted hereunder will terminate automatically
                         ^^^^^^^^^
"terminate" is wordy or unneeded on line 200 at column 50
-------------
termination will not terminate the licences of any person who has received
                     ^^^^^^^^^
"terminate" is wordy or unneeded on line 202 at column 21
-------------
ment between the Parties as to the Work. If any provision of the
                         ^^^^^
"as to" is wordy or unneeded on line 209 at column 30
-------------
provision will be construed or reformed so as necessary to make it valid
               ^^^^^^^^^^^^
"be construed" may be passive voice on line 212 at column 15
-------------
Appendix, so far this is required and reasonable, without reducing the
                      ^^^^^^^^^^^
"is required" may be passive voice on line 215 at column 22
-------------
will be published with a unique version number. All linguistic versions of
     ^^^^^^^^^^^^
"be published" may be passive voice on line 217 at column 5
-------------
- this Licence shall be governed by the law of the European Union Member
               ^^^^^
"shall" is wordy or unneeded on line 239 at column 15
-------------
- this Licence shall be governed by the law of the European Union Member
                     ^^^^^^^^^^^
"be governed" may be passive voice on line 239 at column 21
-------------
- this licence shall be governed by Belgian law if the Licensor has no
               ^^^^^
"shall" is wordy or unneeded on line 242 at column 15
-------------
- this licence shall be governed by Belgian law if the Licensor has no
                     ^^^^^^^^^^^
"be governed" may be passive voice on line 242 at column 21
-------------
  seat, residence or registered office inside a European Union Member
        ^^^^^^^^^
"residence" is wordy or unneeded on line 243 at column 8


In ./docs/community/contributing.md
=============
Thank you for being interested in contributing to checkconnect. There are
              ^^^^^^^^^^^^^^^^
"being interested" may be passive voice on line 3 at column 14
-------------
many ways you can contribute to the project:
^^^^
"many" is a weasel word and can weaken meaning on line 4 at column 0
-------------
- [Implement new features](https://github.com/jmuelbert/checkconnect/issues?q=is
   ^^^^^^^^^
"Implement" is wordy or unneeded on line 8 at column 3
-------------
- Participate in discussions
  ^^^^^^^^^^^
"Participate" is wordy or unneeded on line 11 at column 2
-------------
Possible bugs may be raised as a "Potential Issue" discussion, feature
                  ^^^^^^^^^
"be raised" may be passive voice on line 20 at column 18
-------------
requests may be raised as an "Ideas" discussion. We can then determine if
             ^^^^^^^^^
"be raised" may be passive voice on line 21 at column 13
-------------
the discussion needs to be escalated into an "Issue" or not, or if we'd
                        ^^^^^^^^^^^^
"be escalated" may be passive voice on line 22 at column 24
-------------
Build and validate the documentation website:
          ^^^^^^^^
"validate" is wordy or unneeded on line 110 at column 10


In ./docs/community/code_of_conduct.md
=============
- Giving and gracefully accepting constructive feedback
             ^^^^^^^^^^
"gracefully" can weaken meaning on line 22 at column 13
-------------
sing on what is best not just for us as individuals, but for the
                         ^^^^
"just" can weaken meaning on line 25 at column 31
-------------
  overall community
  ^^^^^^^
"overall" is wordy or unneeded on line 26 at column 2
-------------
t which could reasonably be considered inappropriate in a
                         ^^^^^^^^^^^^^
"be considered" may be passive voice on line 37 at column 39
-------------
nacceptable behavior may be
                         ^^^^^^^^^^^
"be
reported" may be passive voice on line 62 at column 72
-------------
il]. All complaints will be reviewed and
                         ^^^^^^^^^^^
"be reviewed" may be passive voice on line 64 at column 51
-------------
investigated promptly and fairly.
             ^^^^^^^^
"promptly" can weaken meaning on line 65 at column 13
-------------
nvestigated promptly and fairly.
                         ^^^^^^
"fairly" is a weasel word and can weaken meaning on line 65 at column 26
-------------
All community leaders are obligated to respect the privacy and security of
                      ^^^^^^^^^^^^^
"are obligated" may be passive voice on line 67 at column 22
-------------
te. A public apology may be requested.
                         ^^^^^^^^^^^^
"be requested" may be passive voice on line 83 at column 57
-------------
ing the Code of Conduct, is allowed during
                         ^^^^^^^^^^
"is allowed" may be passive voice on line 105 at column 54
-------------
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
                     ^^^^^^^^^^
"is adapted" may be passive voice on line 120 at column 21
-------------
munity Impact Guidelines were inspired by
                         ^^^^^^^^^^^^^
"were inspired" may be passive voice on line 124 at column 28


In ./docs/guides/install.md
=============
vailable on PyPI and can be installed with
                         ^^^^^^^^^^^^
"be installed" may be passive voice on line 13 at column 42


In ./docs/developer/changelog.md
=============
ges to CheckConnect will be documented in this file.
                         ^^^^^^^^^^^^^
"be documented" may be passive voice on line 5 at column 41
-------------
The format is based on
           ^^^^^^^^
"is based" may be passive voice on line 7 at column 11


In ./docs/index.md
=============
checkconnect is distributed under the terms of the
             ^^^^^^^^^^^^^^
"is distributed" may be passive voice on line 34 at column 13
-------------
AJOR.MINOR' versions can be chosen by using
                         ^^^^^^^^^
"be chosen" may be passive voice on line 39 at column 54
-------------
that have not yet been released.
                  ^^^^^^^^^^^^^
"been released" may be passive voice on line 41 at column 18


In ./README.md
=============
is received within a certain time, it means that the web address or the NTP
^^^^^^^^^^^
"is received" may be passive voice on line 29 at column 0
-------------
vailable. If no response is received or an error occurs, it
                         ^^^^^^^^^^^
"is received" may be passive voice on line 30 at column 36
-------------
tion][documentation-url] is made with
                         ^^^^^^^
"is made" may be passive voice on line 48 at column 39
-------------
mkdocs-material-url] and is hosted by
                         ^^^^^^^^^
"is hosted" may be passive voice on line 49 at column 47
-------------
Many thanks to everyone reporting issues.
^^^^
"Many" is a weasel word and can weaken meaning on line 80 at column 0
-------------
checkconnect is distributed under the terms of the
             ^^^^^^^^^^^^^^
"is distributed" may be passive voice on line 86 at column 13

@jmuelbert jmuelbert enabled auto-merge (squash) January 28, 2025 10:14
@jmuelbert jmuelbert merged commit cd4665e into main Jan 28, 2025
9 of 18 checks passed
@jmuelbert jmuelbert deleted the dependabot/npm_and_yarn/npm_and_yarn-c9e65f8b7e branch January 28, 2025 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant