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

Implement Paligo plugin #75

Closed
baruchiro opened this issue May 18, 2023 · 0 comments · Fixed by #78
Closed

Implement Paligo plugin #75

baruchiro opened this issue May 18, 2023 · 0 comments · Fixed by #78
Assignees

Comments

@baruchiro
Copy link
Contributor

Implement the Paligo scanner from inside Checkmarx and run it in parallel with the current implementation in Checkmarx to compare the results and replace it.

@baruchiro baruchiro self-assigned this May 18, 2023
baruchiro pushed a commit that referenced this issue Jun 5, 2023
- get folders and components
- handle only `component` and `folder` types
- send content to items
- avoid reaching the rate limit

Note we are handling only `folder`s to find sub-folders or `components`,
and reading only the `component` (document) content.

### Rate Limit

The rate limit **per minute** described
[here](https://paligo.net/docs/apidocs/en/index-en.html#UUID-a5b548af-9a37-d305-f5a8-11142d86fe20).
The core lib `time/rate` is limiting the rate **per second**. That's why
I'm starting with open seats for all the requests-per-minute, in case
there are fewer requests than the limit. After the first
too-many-requests error, I'm reducing the available seats to 1, so the
frequency of the requests will not reach the rate limit.

Close #75
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

1 participant