gobra | modular verifier for Go programs
kandi X-RAY | gobra Summary
kandi X-RAY | gobra Summary
gobra is a Scala library. gobra has no bugs, it has no vulnerabilities and it has low support. However gobra has a Non-SPDX License. You can download it from GitHub.
Gobra is a prototype verifier for Go programs, based on the Viper verification infrastructure. We call annotated Go programs Gobra programs and use the file extension .gobra for them. A tutorial can be found in docs/tutorial.md. More examples can be found in src/test/resources.
Gobra is a prototype verifier for Go programs, based on the Viper verification infrastructure. We call annotated Go programs Gobra programs and use the file extension .gobra for them. A tutorial can be found in docs/tutorial.md. More examples can be found in src/test/resources.
Support
Quality
Security
License
Reuse
Support
gobra has a low active ecosystem.
It has 74 star(s) with 24 fork(s). There are 8 watchers for this library.
It had no major release in the last 12 months.
There are 71 open issues and 206 have been closed. On average issues are closed in 192 days. There are 13 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of gobra is v23.02
Quality
gobra has no bugs reported.
Security
gobra has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
gobra has a Non-SPDX License.
Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.
Reuse
gobra releases are available to install and integrate.
Installation instructions are available. Examples and code snippets are not available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gobra
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of gobra
gobra Key Features
No Key Features are available at this moment for gobra.
gobra Examples and Code Snippets
No Code Snippets are available at this moment for gobra.
Community Discussions
No Community Discussions are available at this moment for gobra.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install gobra
To switch to tag X, execute the command git checkout X inside the cloned repository.
Create a folder for your Gobra development. We will refer to this folder as gobraHome.
Clone Gobra and Viper dependencies Change directory to gobraHome silver (commit 7228e7144d41c91f02a70a68a93b6b3efae57d14) silicon (commit edb5d079f327c2d9e7eebea9719032c9e70dea37) carbon (commit 4393d154a5ae24d994a0c2c578374bdd49c3a3b3) viperserver (commit 5907ce1744501b7949d25cc0d5356145431ab6f7) Gobra To switch to tag X, execute the command git checkout X inside the cloned repository.
Add symbolic links To create a symbolic link from A to B, you have to run mklink /D A B (Windows (as admin)) resp. ln -s B A (Linux & macOS) (use forward instead of backward slashes in the following) Change directory to gobraHome/silicon and create the symbolic links: silver -> ..\silver Change directory to gobraHome/carbon and create the symbolic links: silver -> ..\silver Change directory to gobraHome/viperserver and create the symbolic links: silver -> ..\silver silicon -> ..\silicon carbon -> ..\carbon Change to gobraHome/gobra and create the links: silver -> ..\silver silicon -> ..\silicon carbon -> ..\carbon viperserver -> ..\viperserver
Install Z3 and Boogie. Steps (iii) and (iv) are specific to Boogie and only necessary when using Carbon as verification backend. Gobra uses the Silicon verification backend by default. Get a Z3 executable. A precompiled executable can be downloaded here. We tested version 4.8.7 64-Bit. Set the environment variable Z3_EXE to the path of your Z3 executable. Get a Boogie executable. Instructions for compilation are given here. Mono is required on Linux and macOS to run Boogie. Alternatively, extract a compiled version from the Viper release tools (Windows, Linux, macOS). Set the environment variable BOOGIE_EXE to the path of your Boogie executable.
Create a folder for your Gobra development. We will refer to this folder as gobraHome.
Clone Gobra and Viper dependencies Change directory to gobraHome silver (commit 7228e7144d41c91f02a70a68a93b6b3efae57d14) silicon (commit edb5d079f327c2d9e7eebea9719032c9e70dea37) carbon (commit 4393d154a5ae24d994a0c2c578374bdd49c3a3b3) viperserver (commit 5907ce1744501b7949d25cc0d5356145431ab6f7) Gobra To switch to tag X, execute the command git checkout X inside the cloned repository.
Add symbolic links To create a symbolic link from A to B, you have to run mklink /D A B (Windows (as admin)) resp. ln -s B A (Linux & macOS) (use forward instead of backward slashes in the following) Change directory to gobraHome/silicon and create the symbolic links: silver -> ..\silver Change directory to gobraHome/carbon and create the symbolic links: silver -> ..\silver Change directory to gobraHome/viperserver and create the symbolic links: silver -> ..\silver silicon -> ..\silicon carbon -> ..\carbon Change to gobraHome/gobra and create the links: silver -> ..\silver silicon -> ..\silicon carbon -> ..\carbon viperserver -> ..\viperserver
Install Z3 and Boogie. Steps (iii) and (iv) are specific to Boogie and only necessary when using Carbon as verification backend. Gobra uses the Silicon verification backend by default. Get a Z3 executable. A precompiled executable can be downloaded here. We tested version 4.8.7 64-Bit. Set the environment variable Z3_EXE to the path of your Z3 executable. Get a Boogie executable. Instructions for compilation are given here. Mono is required on Linux and macOS to run Boogie. Alternatively, extract a compiled version from the Viper release tools (Windows, Linux, macOS). Set the environment variable BOOGIE_EXE to the path of your Boogie executable.
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page
