Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / tomasbjerre/violations-lib issues and pull requests
#190 - 1.157.2 silently upgraded to Java 17
Issue -
State: closed - Opened by TWiStErRob 5 months ago
- 4 comments
#189 - No support of originalUriBaseIds and uriBaseId from sarif files
Issue -
State: closed - Opened by guilcy 5 months ago
- 1 comment
#188 - Repeated message in the Coverity parser.
Issue -
State: closed - Opened by josejobin45 10 months ago
- 5 comments
#187 - feat: coverity parser (refs #186)
Pull Request -
State: closed - Opened by tomasbjerre 10 months ago
#186 - Add coverity parser
Issue -
State: closed - Opened by josejobin45 10 months ago
- 11 comments
#185 - make flake8 regex more precise to avoid false positives
Pull Request -
State: closed - Opened by henglert 11 months ago
- 3 comments
#184 - Flake8 parser regex too unspecific
Issue -
State: closed - Opened by henglert 11 months ago
- 5 comments
#183 - Fix regex to allow for installation of MsBuild in Program Files (x86)
Pull Request -
State: closed - Opened by arontsang over 1 year ago
- 9 comments
#182 - MSBuildLogParser does not support installations of MsBuild on x64 Windows
Issue -
State: closed - Opened by arontsang over 1 year ago
#181 - CodeClimate issue fingerprint clash
Issue -
State: closed - Opened by darekxan over 1 year ago
- 2 comments
#180 - failar test
Pull Request -
State: closed - Opened by tomasbjerre over 1 year ago
#179 - Massive speed regression when processing lots of files
Issue -
State: closed - Opened by Daimanta over 1 year ago
- 1 comment
#178 - Add Spotbugs missing class and error reports.
Issue -
State: open - Opened by fcgxz2003 over 1 year ago
- 3 comments
#177 - Add new Parser to support OWASP Dependency Check files
Issue -
State: closed - Opened by DavidHaasz almost 2 years ago
- 4 comments
#176 - KotlinGradleParser doesn't detect warnings and errors
Issue -
State: closed - Opened by cosminstefanxp almost 2 years ago
- 1 comment
#175 - Bandit format not parsing
Issue -
State: closed - Opened by bmagistro almost 2 years ago
- 1 comment
#174 - fix: rule resolution in sarif
Pull Request -
State: closed - Opened by bug-brain almost 2 years ago
- 1 comment
#173 - JUnit Message contains the whole stacktrace
Issue -
State: closed - Opened by oers almost 2 years ago
- 7 comments
#172 - Dependency Check plugin parser/support
Issue -
State: closed - Opened by spyhunter99 almost 2 years ago
- 1 comment
#171 - Added parser for semgrep
Pull Request -
State: closed - Opened by ateglas about 2 years ago
- 1 comment
#170 - Please add support for generic issues parser
Issue -
State: closed - Opened by CarstenGrohmann about 2 years ago
- 4 comments
#169 - Show better error message for unknown parsers
Issue -
State: open - Opened by CarstenGrohmann about 2 years ago
- 1 comment
#168 - CodeClimateTransformer - HTML in FindBugs messages
Issue -
State: open - Opened by PaulCormier about 2 years ago
- 1 comment
#167 - FindbugsParser - Remove bug details from message field
Issue -
State: open - Opened by PaulCormier about 2 years ago
- 1 comment
#166 - I am unable to parse a report
Issue -
State: closed - Opened by WoodyAsterisk over 2 years ago
- 1 comment
#165 - Fixes #153: Handle absolute Windows paths in ErrorProne warnings
Pull Request -
State: closed - Opened by tnl-tbi over 2 years ago
- 1 comment
#164 - feat: #160 #163 unique correlation id + rule message display
Pull Request -
State: closed - Opened by ejohn20 over 2 years ago
#163 - SARIF Parser fails to add multiple results with the same rule id
Issue -
State: closed - Opened by ejohn20 over 2 years ago
#162 - CI is not required
Issue -
State: closed - Opened by TWiStErRob over 2 years ago
- 1 comment
#161 - Fix typo in SarifParserTest
Pull Request -
State: closed - Opened by TWiStErRob over 2 years ago
#160 - SARIF 2.1.0 Support Results Missing Location
Issue -
State: closed - Opened by ejohn20 over 2 years ago
- 4 comments
#159 - fix: stepping dependencies
Pull Request -
State: closed - Opened by tomasbjerre over 2 years ago
#158 - SARIF 2.1.0 messages with placeholders
Issue -
State: closed - Opened by KalleOlaviNiemitalo over 2 years ago
- 1 comment
#157 - SARIF 2.1.0 message string lookup
Issue -
State: closed - Opened by KalleOlaviNiemitalo over 2 years ago
- 5 comments
#156 - SARIF 2.1.0 discard suppressed results
Issue -
State: closed - Opened by KalleOlaviNiemitalo over 2 years ago
- 7 comments
#155 - Category from Roslyn SARIF 2.1.0 log
Issue -
State: closed - Opened by KalleOlaviNiemitalo over 2 years ago
- 4 comments
#154 - SARIF 2.1.0 toolExecutionNotifications, toolConfigurationNotifications
Issue -
State: closed - Opened by KalleOlaviNiemitalo over 2 years ago
- 4 comments
#153 - ErrorProne parser fails on Windows paths
Issue -
State: closed - Opened by tnl-tbi over 2 years ago
- 1 comment
#152 - Favor Markdown from Sarif Reports
Pull Request -
State: closed - Opened by jeremylong over 2 years ago
- 1 comment
#151 - Use OWASP Java Encoder
Pull Request -
State: open - Opened by jeremylong over 2 years ago
- 2 comments
#150 - Sarif Rule Help Text
Pull Request -
State: closed - Opened by jeremylong over 2 years ago
- 1 comment
#149 - Sarif Reporter Fix
Pull Request -
State: closed - Opened by jeremylong over 2 years ago
- 2 comments
#148 - feat: Add GreenHills log parser.
Pull Request -
State: closed - Opened by falkena over 2 years ago
- 1 comment
#147 - Documentation: SARIF: Only v2.x is supported, analysis fails with SARIF v1.x files
Issue -
State: closed - Opened by jachstet-sea almost 3 years ago
- 1 comment
#146 - testning...
Pull Request -
State: closed - Opened by tomasbjerre almost 3 years ago
#145 - Parse JUnit skipped tests as warnings
Issue -
State: open - Opened by TWiStErRob almost 3 years ago
- 1 comment
#144 - SARIF Issue Severity Always INFO
Issue -
State: closed - Opened by JoshStutts almost 3 years ago
- 2 comments
#143 - Valid Sarif file fails with NullPointerException
Issue -
State: closed - Opened by Olstyle almost 3 years ago
- 6 comments
#142 - dart/flutter analyze
Issue -
State: closed - Opened by twogood about 3 years ago
- 2 comments
#141 - add paths to valgrind Violation.file
Pull Request -
State: closed - Opened by bitrunner about 3 years ago
- 1 comment
#140 - testing
Pull Request -
State: closed - Opened by tomasbjerre about 3 years ago
#139 - fix valgrind suppression parsing
Pull Request -
State: closed - Opened by bitrunner about 3 years ago
- 1 comment
#138 - add valgrind xml output parser
Pull Request -
State: closed - Opened by bitrunner about 3 years ago
- 2 comments
#137 - test
Pull Request -
State: closed - Opened by tomasbjerre about 3 years ago
#136 - CppCheck reports the column too.
Issue -
State: closed - Opened by ferkulat about 3 years ago
- 2 comments
#135 - [Question] What's the best way to use `violations-lib` from GitHub Actions?
Issue -
State: closed - Opened by leinardi about 3 years ago
- 4 comments
#134 - Idea: add support for "Static Analysis Results Interchange Format (SARIF)"
Issue -
State: closed - Opened by ZyanKLee about 3 years ago
- 3 comments
#133 - `CodeClimateParser` should map `engine_name` to `reporter`
Issue -
State: closed - Opened by remal over 3 years ago
- 1 comment
#132 - `CodeClimateParser` should map `check_name` to `rule`
Issue -
State: closed - Opened by remal over 3 years ago
- 1 comment
#131 - Support for Cfn-Lint reports in Junit format
Issue -
State: closed - Opened by chilcano over 3 years ago
- 1 comment
#130 - Generated code fails to parse because it does not have line information
Pull Request -
State: closed - Opened by ateglas over 3 years ago
- 2 comments
#129 - WIP: Added starting point for Jacoco coverage parser
Pull Request -
State: closed - Opened by ateglas over 3 years ago
- 4 comments
#128 - Support for jacoco code coverage
Issue -
State: closed - Opened by ateglas over 3 years ago
- 6 comments
#127 - add parser for msbuild log files
Pull Request -
State: closed - Opened by miikeat over 3 years ago
- 2 comments
#126 - StyleCop Analyzer not generating an xml anymore
Issue -
State: closed - Opened by miikeat over 3 years ago
- 9 comments
#125 - Support the hadolint format
Issue -
State: closed - Opened by benmathews over 3 years ago
- 1 comment
#124 - JUnit parser cannot parse reports with plain errors
Issue -
State: closed - Opened by uhafner almost 4 years ago
- 1 comment
#123 - Optionally relativize paths in CodeClimate output
Issue -
State: closed - Opened by fgabolde almost 4 years ago
- 2 comments
Labels: enhancement
#122 - Mypy parse doesn't send any errors due to "unchanged files"
Issue -
State: closed - Opened by ivan-bilan almost 4 years ago
- 6 comments
#121 - New Android Severity Fatal
Issue -
State: closed - Opened by NitroG42 almost 4 years ago
- 1 comment
#120 - Failures of architecture tests are not detected
Issue -
State: closed - Opened by uhafner almost 4 years ago
- 1 comment
#119 - Parse CPPCheck reports without file #118
Pull Request -
State: closed - Opened by tomasbjerre about 4 years ago
- 2 comments
#118 - CppCheck parser ignores errors without location
Issue -
State: closed - Opened by uhafner about 4 years ago
- 2 comments
#117 - prevent comment line out of diff
Pull Request -
State: closed - Opened by Nov1kov about 4 years ago
- 3 comments
#116 - fix parse gradle kotlin column line
Pull Request -
State: closed - Opened by Nov1kov about 4 years ago
- 3 comments
#115 - JUnit parser does not detect a failure
Issue -
State: closed - Opened by uhafner about 4 years ago
- 1 comment
#114 - Gracefully allow tosca generated incomplete input files
Issue -
State: closed - Opened by carstenartur over 4 years ago
- 6 comments
#113 - JUnit parser throws StringIndexOutOfBoundsException
Issue -
State: closed - Opened by uhafner over 4 years ago
- 2 comments
#112 - Add rule to code climate report
Issue -
State: closed - Opened by sniperrifle2004 over 4 years ago
- 1 comment
#111 - Check "Notes" Section!!
Pull Request -
State: closed - Opened by AmitNayak9 over 4 years ago
- 1 comment
#110 - Rewriting CPPCheckParser parser #101
Pull Request -
State: closed - Opened by tomasbjerre over 4 years ago
#109 - Rewriting JUnit parser #108 #101
Pull Request -
State: closed - Opened by tomasbjerre over 4 years ago
#108 - Parse jest-junit
Issue -
State: closed - Opened by tomasbjerre over 4 years ago
#107 - Checkstyle: don't fail if line attribute is not present
Issue -
State: closed - Opened by fouadchamoun over 4 years ago
- 5 comments
#106 - Generic Parser comments as a Single Line
Issue -
State: closed - Opened by anirudhbagri over 4 years ago
- 10 comments
Labels: question
#105 - Resolve complete source path when parsing Spotbugs xml file
Issue -
State: closed - Opened by terje2001 over 4 years ago
- 2 comments
#104 - add file parser #103
Pull Request -
State: closed - Opened by anirudhbagri over 4 years ago
- 1 comment
#103 - Add a basic generic Parser
Issue -
State: closed - Opened by anirudhbagri over 4 years ago
- 1 comment
#102 - WIP: DiffParser #95
Pull Request -
State: closed - Opened by tomasbjerre over 4 years ago
#101 - Replace the regexp xml-parsing with STL xml parser
Issue -
State: closed - Opened by tomasbjerre over 4 years ago
#100 - JUnit failures without type or message will be skipped
Issue -
State: closed - Opened by SilkyChickn over 4 years ago
- 7 comments
#99 - Show character instead of HTML Character code after comment POST
Issue -
State: closed - Opened by anirudhbagri over 4 years ago
- 1 comment
#98 - compareTo method of Violation is broken and filters too many unique warnings
Issue -
State: closed - Opened by uhafner over 4 years ago
- 1 comment
#97 - NoSuchElementException when parsing JUnit report without type
Issue -
State: closed - Opened by uhafner over 4 years ago
- 2 comments
#96 - NumberFormatException thrown by ErrorProne parser
Issue -
State: open - Opened by djh82 over 4 years ago
- 2 comments
#95 - Add support for "suggested change"
Issue -
State: open - Opened by nedtwigg over 4 years ago
- 3 comments
Labels: enhancement
#94 - Fix MyPy parser swallowing parts of error message
Pull Request -
State: closed - Opened by yayachiken over 4 years ago
- 3 comments
#93 - Support Lizard
Issue -
State: closed - Opened by janakaaleph over 4 years ago
- 1 comment
#92 - Configure Renovate
Pull Request -
State: closed - Opened by renovate[bot] over 4 years ago
#91 - Can't parse Junit5 (Jupiter) report
Issue -
State: closed - Opened by tobimichael96 over 4 years ago
- 2 comments