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.

Sign up for GitHub

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

Jump to bottom

Ability to check access tokens #182

Merged
merged 4 commits into from
May 29, 2024
Merged

Ability to check access tokens #182

merged 4 commits into from
May 29, 2024

Conversation

raz-shlomo-frontegg
Copy link
Collaborator

No description provided.

@github-actions GitHub Actions
Copy link 

# npm audit report

express  <4.19.2
Severity: moderate
Express.js Open Redirect in malformed URLs - https://github.com/advisories/GHSA-rv95-896h-c2vc
fix available via `npm audit fix`
node_modules/express

follow-redirects  <=1.15.5
Severity: moderate
follow-redirects' Proxy-Authorization header kept across hosts - https://github.com/advisories/GHSA-cxjh-pqwp-8mfp
fix available via `npm audit fix`
node_modules/follow-redirects

ip  2.0.0
Severity: moderate
NPM IP package incorrectly identifies some private IP addresses as public - https://github.com/advisories/GHSA-78xj-cgh5-2h22
fix available via `npm audit fix`
node_modules/npm/node_modules/ip

tar  <6.2.1
Severity: moderate
Denial of service while parsing a tar file due to lack of folders count validation - https://github.com/advisories/GHSA-f5x3-32g6-xq36
fix available via `npm audit fix --force`
Will install semantic-release@23.1.1, which is a breaking change
node_modules/npm/node_modules/tar
  npm  <=10.5.0
  Depends on vulnerable versions of tar
  node_modules/npm
    @semantic-release/npm  5.0.0 - 10.0.6
    Depends on vulnerable versions of npm
    node_modules/@semantic-release/npm
      semantic-release  15.9.4 - 22.0.0-beta.9
      Depends on vulnerable versions of @semantic-release/npm
      node_modules/semantic-release

7 moderate severity vulnerabilities

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

@github-actions GitHub Actions
Copy link 

# npm audit report

ip  2.0.0
Severity: moderate
NPM IP package incorrectly identifies some private IP addresses as public - https://github.com/advisories/GHSA-78xj-cgh5-2h22
fix available via `npm audit fix`
node_modules/npm/node_modules/ip

tar  <6.2.1
Severity: moderate
Denial of service while parsing a tar file due to lack of folders count validation - https://github.com/advisories/GHSA-f5x3-32g6-xq36
fix available via `npm audit fix --force`
Will install semantic-release@23.1.1, which is a breaking change
node_modules/npm/node_modules/tar
  npm  <=10.5.0
  Depends on vulnerable versions of tar
  node_modules/npm
    @semantic-release/npm  5.0.0 - 10.0.6
    Depends on vulnerable versions of npm
    node_modules/@semantic-release/npm
      semantic-release  15.9.4 - 22.0.0-beta.9
      Depends on vulnerable versions of @semantic-release/npm
      node_modules/semantic-release

5 moderate severity vulnerabilities

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

@raz-shlomo-frontegg raz-shlomo-frontegg enabled auto-merge (squash) May 29, 2024 14:32
@github-actions GitHub Actions
Copy link 

# npm audit report

ip  2.0.0
Severity: moderate
NPM IP package incorrectly identifies some private IP addresses as public - https://github.com/advisories/GHSA-78xj-cgh5-2h22
fix available via `npm audit fix`
node_modules/npm/node_modules/ip

tar  <6.2.1
Severity: moderate
Denial of service while parsing a tar file due to lack of folders count validation - https://github.com/advisories/GHSA-f5x3-32g6-xq36
fix available via `npm audit fix --force`
Will install semantic-release@23.1.1, which is a breaking change
node_modules/npm/node_modules/tar
  npm  <=10.5.0
  Depends on vulnerable versions of tar
  node_modules/npm
    @semantic-release/npm  5.0.0 - 10.0.6
    Depends on vulnerable versions of npm
    node_modules/@semantic-release/npm
      semantic-release  15.9.4 - 22.0.0-beta.9
      Depends on vulnerable versions of @semantic-release/npm
      node_modules/semantic-release

5 moderate severity vulnerabilities

To address issues that do not require attention, run:
  npm audit fix

To address all issues (including breaking changes), run:
  npm audit fix --force

@raz-shlomo-frontegg raz-shlomo-frontegg merged commit 2559de7 into next May 29, 2024
9 of 10 checks passed
raz-shlomo-frontegg added a commit that referenced this pull request May 29, 2024
@raz-shlomo-frontegg
fix(access-token): Ability to check access tokens (#182)
d530701
raz-shlomo-frontegg added a commit that referenced this pull request May 29, 2024
@raz-shlomo-frontegg
fix(access-token): Ability to check access tokens (#182)
f4615cc
raz-shlomo-frontegg added a commit that referenced this pull request May 29, 2024
@raz-shlomo-frontegg
fix(access-token): Ability to check access tokens (#182) (#183)
7544765
guy-frontegg pushed a commit that referenced this pull request May 29, 2024
@semantic-release-bot
chore(release): 5.3.0-alpha.6 [skip ci]
f262044 
# [5.3.0-alpha.6](5.3.0-alpha.5...5.3.0-alpha.6) (2024-05-29)

### Bug Fixes

* **access-token:** Ability to check access tokens ([#182](#182)) ([d530701](d530701))
* **access-token:** Ability to check access tokens ([#182](#182)) ([#183](#183)) ([7544765](7544765))
guy-frontegg pushed a commit that referenced this pull request Jun 2, 2024
@semantic-release-bot
chore(release): 5.3.1-alpha.1 [skip ci]
b047ddb 
## [5.3.1-alpha.1](5.3.0...5.3.1-alpha.1) (2024-06-02)

### Bug Fixes

* **access-token:** Ability to check access tokens ([#182](#182)) ([d530701](d530701))
* **access-token:** Ability to check access tokens ([#182](#182)) ([#183](#183)) ([7544765](7544765))
Omers-Frontegg pushed a commit that referenced this pull request Jun 2, 2024
@raz-shlomo-frontegg @semantic-release-bot
FIx(access-tokens): Bug fixes (#184)
1854627 
* Ability to check access tokens (#182)

* iterate over all resolvers

* audit fix

* fix warning and test

* fix warning and test

* fix(access-token): Ability to check access tokens (#182)

* fix(access-token): Ability to check access tokens (#182) (#183)

* chore(release): 5.3.0-alpha.6 [skip ci]

# [5.3.0-alpha.6](5.3.0-alpha.5...5.3.0-alpha.6) (2024-05-29)

### Bug Fixes

* **access-token:** Ability to check access tokens ([#182](#182)) ([d530701](d530701))
* **access-token:** Ability to check access tokens ([#182](#182)) ([#183](#183)) ([7544765](7544765))

* chore(release): 5.3.1-alpha.1 [skip ci]

## [5.3.1-alpha.1](5.3.0...5.3.1-alpha.1) (2024-06-02)

### Bug Fixes

* **access-token:** Ability to check access tokens ([#182](#182)) ([d530701](d530701))
* **access-token:** Ability to check access tokens ([#182](#182)) ([#183](#183)) ([7544765](7544765))

---------

Co-authored-by: semantic-release-bot <semantic-release-bot@martynus.net>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@Omers-Frontegg Omers-Frontegg Omers-Frontegg approved these changes

@eran-frontegg eran-frontegg eran-frontegg approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@raz-shlomo-frontegg @eran-frontegg @Omers-Frontegg