Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / NeuraLegion/sectester-js issues and pull requests
#97 - fix(scan): change the condition members' precedence
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#96 - Condition members' precedence
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: bug
#96 - Condition members' precedence
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: bug
#95 - ci: pass arguments to `format:check` properly
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
Labels: Type: tooling
#95 - ci: pass arguments to `format:check` properly
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
Labels: Type: tooling
#95 - ci: pass arguments to `format:check` properly
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
Labels: Type: tooling
#94 - fix(scan): truncate a file name if a length exceeds the limit
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#94 - fix(scan): truncate a file name if a length exceeds the limit
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#94 - fix(scan): truncate a file name if a length exceeds the limit
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#93 - File name is too long
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: bug
#93 - File name is too long
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: bug
#93 - File name is too long
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: bug
#92 - refactor(bus): log the data flow
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#92 - refactor(bus): log the data flow
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#91 - Data flow should be logged
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: technical debt
#91 - Data flow should be logged
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: technical debt
#91 - Data flow should be logged
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: technical debt
#91 - Data flow should be logged
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: technical debt
#90 - fix(bus): fallback to a message if body is stream
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#90 - fix(bus): fallback to a message if body is stream
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#90 - fix(bus): fallback to a message if body is stream
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#90 - fix(bus): fallback to a message if body is stream
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#89 - refactor(bus): humanize axios error messages
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
Labels: Type: refactoring
#89 - refactor(bus): humanize axios error messages
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
Labels: Type: refactoring
#88 - Humanize axios error messages
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: technical debt
#88 - Humanize axios error messages
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: technical debt
#88 - Humanize axios error messages
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: technical debt
#88 - Humanize axios error messages
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: technical debt
#87 - fix(scan): raise an exception if scan enters into `queued` status
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#87 - fix(scan): raise an exception if scan enters into `queued` status
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#86 - fix(core): use the repo name as the client name in analytics
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#86 - fix(core): use the repo name as the client name in analytics
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#85 - Use the repo name as the client name in the analytics
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: bug
#85 - Use the repo name as the client name in the analytics
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: bug
#85 - Use the repo name as the client name in the analytics
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: bug
#85 - Use the repo name as the client name in the analytics
Issue -
State: closed - Opened by derevnjuk over 2 years ago
Labels: Type: bug
#84 - fix(bus): handle Node.js error codes first
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#84 - fix(bus): handle Node.js error codes first
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#84 - fix(bus): handle Node.js error codes first
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#84 - fix(bus): handle Node.js error codes first
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#83 - docs: clarify which API keys type to use
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#83 - docs: clarify which API keys type to use
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#83 - docs: clarify which API keys type to use
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#83 - docs: clarify which API keys type to use
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#82 - fix(scan): disallow setting the name longer than 200 characters
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#82 - fix(scan): disallow setting the name longer than 200 characters
Pull Request -
State: closed - Opened by derevnjuk over 2 years ago
- 1 comment
#81 - fix(scan): handle an error on stopping a scan
Pull Request -
State: closed - Opened by derevnjuk almost 3 years ago
- 1 comment
Labels: Type: bug
#81 - fix(scan): handle an error on stopping a scan
Pull Request -
State: closed - Opened by derevnjuk almost 3 years ago
- 1 comment
Labels: Type: bug
#81 - fix(scan): handle an error on stopping a scan
Pull Request -
State: closed - Opened by derevnjuk almost 3 years ago
- 1 comment
Labels: Type: bug
#81 - fix(scan): handle an error on stopping a scan
Pull Request -
State: closed - Opened by derevnjuk almost 3 years ago
- 1 comment
Labels: Type: bug
#80 - Unexpected an error message due to trying to stop a done scan
Issue -
State: closed - Opened by derevnjuk almost 3 years ago
Labels: Type: bug, Priority: medium
#80 - Unexpected an error message due to trying to stop a done scan
Issue -
State: closed - Opened by derevnjuk almost 3 years ago
Labels: Type: bug, Priority: medium
#80 - Unexpected an error message due to trying to stop a done scan
Issue -
State: closed - Opened by derevnjuk almost 3 years ago
Labels: Type: bug, Priority: medium
#80 - Unexpected an error message due to trying to stop a done scan
Issue -
State: closed - Opened by derevnjuk almost 3 years ago
Labels: Type: bug, Priority: medium
#77 - fix(scan): define the medium severity range properly
Pull Request -
State: closed - Opened by derevnjuk almost 3 years ago
- 1 comment
Labels: Type: bug
#77 - fix(scan): define the medium severity range properly
Pull Request -
State: closed - Opened by derevnjuk almost 3 years ago
- 1 comment
Labels: Type: bug
#77 - fix(scan): define the medium severity range properly
Pull Request -
State: closed - Opened by derevnjuk almost 3 years ago
- 1 comment
Labels: Type: bug
#77 - fix(scan): define the medium severity range properly
Pull Request -
State: closed - Opened by derevnjuk almost 3 years ago
- 1 comment
Labels: Type: bug
#76 - The medium severity range takes into account low issues instead of high
Issue -
State: closed - Opened by derevnjuk almost 3 years ago
Labels: Priority: high, Type: bug
#76 - The medium severity range takes into account low issues instead of high
Issue -
State: closed - Opened by derevnjuk almost 3 years ago
Labels: Priority: high, Type: bug
#76 - The medium severity range takes into account low issues instead of high
Issue -
State: closed - Opened by derevnjuk almost 3 years ago
Labels: Priority: high, Type: bug
#75 - Some tests result in failure by axios timeout, repeater is not deleted
Issue -
State: closed - Opened by wawaqa almost 3 years ago
- 2 comments
Labels: Type: bug
#75 - Some tests result in failure by axios timeout, repeater is not deleted
Issue -
State: closed - Opened by wawaqa almost 3 years ago
- 2 comments
Labels: Type: bug
#74 - Scans initiated by tests failed by timeout get disrupted
Issue -
State: open - Opened by wawaqa almost 3 years ago
Labels: Type: question
#74 - Scans initiated by tests failed by timeout get disrupted
Issue -
State: open - Opened by wawaqa almost 3 years ago
Labels: Type: question
#74 - Scans initiated by tests failed by timeout get disrupted
Issue -
State: open - Opened by wawaqa almost 3 years ago
Labels: Type: question
#74 - Scans initiated by tests failed by timeout get disrupted
Issue -
State: open - Opened by wawaqa almost 3 years ago
Labels: Type: question
#73 - Jest warning on leaks if tests fail by timeout
Issue -
State: open - Opened by wawaqa almost 3 years ago
- 2 comments
Labels: Priority: low, Type: bug
#73 - Jest warning on leaks if tests fail by timeout
Issue -
State: open - Opened by wawaqa almost 3 years ago
- 2 comments
Labels: Priority: low, Type: bug
#73 - Jest warning on leaks if tests fail by timeout
Issue -
State: open - Opened by wawaqa almost 3 years ago
- 2 comments
Labels: Priority: low, Type: bug
#73 - Jest warning on leaks if tests fail by timeout
Issue -
State: open - Opened by wawaqa almost 3 years ago
- 2 comments
Labels: Priority: low, Type: bug
#71 - Docs improvements
Issue -
State: closed - Opened by dcheremnov almost 3 years ago
- 3 comments
Labels: Type: documentation
#71 - Docs improvements
Issue -
State: closed - Opened by dcheremnov almost 3 years ago
- 3 comments
Labels: Type: documentation
#69 - docs(readme): minor fixes
Pull Request -
State: closed - Opened by pmstss almost 3 years ago
- 1 comment
#69 - docs(readme): minor fixes
Pull Request -
State: closed - Opened by pmstss almost 3 years ago
- 1 comment
#69 - docs(readme): minor fixes
Pull Request -
State: closed - Opened by pmstss almost 3 years ago
- 1 comment
#69 - docs(readme): minor fixes
Pull Request -
State: closed - Opened by pmstss almost 3 years ago
- 1 comment
#68 - Fix README for scan package
Issue -
State: closed - Opened by dcheremnov almost 3 years ago
Labels: Type: documentation
#68 - Fix README for scan package
Issue -
State: closed - Opened by dcheremnov almost 3 years ago
Labels: Type: documentation
#68 - Fix README for scan package
Issue -
State: closed - Opened by dcheremnov almost 3 years ago
Labels: Type: documentation
#68 - Fix README for scan package
Issue -
State: closed - Opened by dcheremnov almost 3 years ago
Labels: Type: documentation
#67 - Fix README for runner package
Issue -
State: closed - Opened by dcheremnov almost 3 years ago
Labels: Type: documentation
#67 - Fix README for runner package
Issue -
State: closed - Opened by dcheremnov almost 3 years ago
Labels: Type: documentation
#67 - Fix README for runner package
Issue -
State: closed - Opened by dcheremnov almost 3 years ago
Labels: Type: documentation
#67 - Fix README for runner package
Issue -
State: closed - Opened by dcheremnov almost 3 years ago
Labels: Type: documentation
#66 - Queued scan results in passed test (no waiting until it starts)
Issue -
State: closed - Opened by wawaqa almost 3 years ago
- 4 comments
Labels: Type: bug
#65 - Taking raw URL as scan name causes 503 error
Issue -
State: closed - Opened by wawaqa almost 3 years ago
Labels: Priority: low, Type: bug
#65 - Taking raw URL as scan name causes 503 error
Issue -
State: closed - Opened by wawaqa almost 3 years ago
Labels: Priority: low, Type: bug
#65 - Taking raw URL as scan name causes 503 error
Issue -
State: closed - Opened by wawaqa almost 3 years ago
Labels: Priority: low, Type: bug
#65 - Taking raw URL as scan name causes 503 error
Issue -
State: closed - Opened by wawaqa almost 3 years ago
Labels: Priority: low, Type: bug
#64 - Using Org API Key results in 401 error
Issue -
State: closed - Opened by wawaqa almost 3 years ago
Labels: Priority: low, Type: bug
#64 - Using Org API Key results in 401 error
Issue -
State: closed - Opened by wawaqa almost 3 years ago
Labels: Priority: low, Type: bug
#63 - fix(*): distribute `commonjs` modules
Pull Request -
State: closed - Opened by derevnjuk almost 3 years ago
- 1 comment
#63 - fix(*): distribute `commonjs` modules
Pull Request -
State: closed - Opened by derevnjuk almost 3 years ago
- 1 comment
#62 - Distribute `commonjs` modules
Issue -
State: closed - Opened by derevnjuk almost 3 years ago
Labels: Type: bug
#62 - Distribute `commonjs` modules
Issue -
State: closed - Opened by derevnjuk almost 3 years ago
Labels: Type: bug
#62 - Distribute `commonjs` modules
Issue -
State: closed - Opened by derevnjuk almost 3 years ago
Labels: Type: bug
#62 - Distribute `commonjs` modules
Issue -
State: closed - Opened by derevnjuk almost 3 years ago
Labels: Type: bug
#61 - fix(bus): adjust axios config to properly handle 204 responses
Pull Request -
State: closed - Opened by pmstss almost 3 years ago
- 2 comments
#60 - `SyntaxError: Unexpected end of JSON input` in `HttpCommandDispatcher` on repeater removal
Issue -
State: closed - Opened by pmstss almost 3 years ago
Labels: Type: bug