Skip to content

This plug-in allows Java and C/C++ Eclipse users to perform static code assessments in the SWAMP and to view the results within the Eclipse Integrated Development Environment. The plug-in can also be found in the Eclipse Marketplace as SWAMP Eclipse Plug-in.

Switch branches/tags

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

SWAMP Eclipse Plug-in User Guide


The Software Assurance Marketplace (SWAMP) hosts a collection of static analysis tools, which look for security vulnerabilities and other bugs in source code. A user can upload code to the SWAMP and get results from having that code assessed on different tools and operating systems. The purpose of this plug-in is to allow users to submit code quickly and easily from the Eclipse Integrated Development Environment.

To use this plug-in, the user must have an account on a SWAMP instance. Users can use the SWAMP hosted at or a SWAMP-in-a-Box instance (see your local support staff). If a user is using a CILogin (university credential or GitHub), he or she will need to make a password for each SWAMP instance he or she wishes to log into.


This document describes the SWAMP Eclipse plug-in, an extension to the Eclipse IDE that allows users with SWAMP accounts to submit Java code to the SWAMP.

1. plug-in installation

To install the Eclipse plug-in, a user may either download the plug-in archive and install it into Eclipse or download the plug-in directly from the Eclipse Marketplace.

1.1. Download and install plug-in

To download and install, follow these steps:

  1. Download the archive from the SWAMP releases page and unzip it.

  2. Open Eclipse Neon (or any version greater than 4.6)

  3. In the menu bar, select "Help > Install New Software".

  4. In the "Install" dialog that comes up, click "Add…​".

  5. In the "Add Repository" dialog that comes up select "Local…​" and select the "update-site" directory inside the directory created from unzipping the archive.

  6. Back in the "Install" dialog, uncheck the "Group items by category" checkbox. The Eclipse plug-in should show up as an option now. Check that checkbox.

  7. Click "Next" and finish the installation. Eclipse will restart and when it reopens, the plug-in should be installed

1.2. Upgrade the plug-in

To upgrade the plugin, start Eclipse, select the Check for Updates item in the Help menu. If there is an update it should be listed in the Available Updates dialog box. Make sure the Swamp plugin is selected and click the Next > button. Next click the Next > button on the Update Details screen. Accept any license agreements and click Finish on the on the Review License screen. Confirm any dialog boxes to finish the installation.

1.3. Eclipse Marketplace

The Eclipse Marketplace hosts plug-ins and features. To access the Eclipse Marketplace, select "Eclipse Marketplace…​" from the Help menu. Search for "SWAMP" and click the install button. When the installation is finished, you should see the SWAMP icon in the toolbar and the SWAMP menu in the menubar (highlighted in the screenshot below).

Menubar and Toolbar

2. Set up plug-in preferences (optional)

2.1. Available SWAMP hosts

For shared Eclipse installations and individual installations, system administrators and users may control what SWAMP hosts are accessible by modifying SWAMP_hosts.json and adding it to the installation directory (this can be found by clicking on Help > Installation Details, switching to the "Configuration" tab, and viewing the value for "eclipse.home.location" in the "System properties" section). By default, the MIR host is available to all users.

2.2. Editor markers

The SWAMP perspective adds colored markers to the left-hand ruler to annotate weaknesses found by the SWAMP. A user may set preferences for these markers by modifying .marker_preferences and copying it to a directory named .SWAMP_SETTINGS in the user’s home directory.

2.3. Using http proxy

The SWAMP plugin versions 1.1.0 and above can work with http proxies. If a https or http proxy is set via standard eclipse proxy configuration, the SWAMP plugin will use the proxy to talk to SWAMP. Incase, if you do not want SWAMP plugin to use the proxy, specify the SWAMP host name in proxy bypass settings.

2.4. Eclipse plugin with Swamp-In-The-Box (SiB) instances

If you are accessing an SiB instance that uses a self-signed SSL/TLS certificate then, the plugin will fail to communicate with that SiB instance. The reason being Java’s security model by default does not allow communicating with a web-service that has a self-signed SSL/TLS certificate. To overcome this restriction, the web-service’s self-signed SSL/TLS certificate has to be added to the Java installation’s default keystore on the machine that is running eclipse . The following are the instructions on how to do it:

  1. Access the SiB from the web-browser and download the SiB’s self-signed certificate by following these instruction here:

  2. Run the following commands to add the self-signed certificate to the Java Installation’s keystore:

  1. Change the present working directory to your Java installation directory + jre/lib/security/.

       cd $JAVA_HOME/jre/lib/security
  2. Make a backup copy of the cacerts file

       cp cacerts cacerts.original
  3. Add the certificate to the keystore (Assuming here that the self-signed certificate is stored on the desktop as

       sudo keytool -importcert -alias sib-name -file ~/Desktop/ -keystore $PWD/cacerts

3. Configuration and submission

3.1. login

A user must be logged into his or her SWAMP account to use the plug-in. To log in, select "Log In" from the SWAMP dropdown menu. The hostname field specifies what SWAMP instance a user logs into. By default, the Morgridge Institute for Research’s hostname is entered. The next two fields are username and password. If logging onto the default SWAMP instance, these are the same credentials used for The plug-in stores cookies with the user’s session information for 24 hours. To log out, select "Log Out" from the SWAMP dropdown menu.

Note: Users with GitHub or InCommon credentials will have to make a new credential for the SWAMP and use that to log in.

Authentication Dialog

3.2. assessment configuration

Any of the open Java projects in a user’s Eclipse workspace may be submitted to the SWAMP. To configure a project, a user simply needs to have some file from the project (e.g. a source code file) active in his or her editor and to select "Configure Assessment Submission" from the SWAMP dropdown menu. If the user is not logged in, the authentication popup will come first allowing the user to authenticate. Once the user is logged in, a dialog with configuration information for the assessment pops up.

Configuration Dialog

3.3. configuration options

  1. SWAMP Project - this is the SWAMP project to which the package belongs (or if it’s a new package, the project to which the package will be added). A user can only select from projects he or she has access to

  2. SWAMP Package - this is the SWAMP package of which a version will be uploaded. This also offers the option to "Create new package"

  3. New Package Name - this is the name of the new package that will be uploaded

  4. Package Version - this is the version of the package that will be uploaded. It defaults to a timestamp of the time at which this dialog was opened

  5. Eclipse Project - this is the Java project in the user’s workspace whose source will be uploaded

  6. Package Type - this is the SWAMP package type of the package. A user may think of the package type as the language version. The valid package types for the Eclipse plug-in are "Java 7, Java 8, and C/C++." In most cases, this will be set automatically based on how the Eclipse project to be assessed is configured.

  7. Build System - this is the build system of the project. If a user selects "Auto-generate build file", the plug-in will create a build file for building the project.

  8. Package System Libraries? - this option allows users to upload the system libraries that Eclipse uses for this project to the SWAMP along with the package. This sets the bootclasspath for the Java compiler. In most cases, this should not be checked as uploading system libraries is time consuming and only provides benefits in certain cases. If a project builds in Eclipse but fails to build in the SWAMP, a user should try uploading system libraries.

  9. Build File - this is the path of the build file to be used (in the case that the plug-in is not auto-generating the build file)

  10. Build Target - this is the target to build the project (in the case that the plug-in is not auto-generating the build file)

3.4. tool selection

Next, a user must select the tools he or she wishes to run the assessments on

Tool Dialog

3.5. platform selection

Finally, a user must select the platforms he or she wishes to run the assessments on. A platform is the operating system that runs on an assessment’s virtual machine. For interpreted languages or languages that run on a VM there will only be one option.

Platform Dialog

3.6. submission

After a user clicks "OK" in the dialog for selecting platforms, a background job is launched. The user’s console will have messages from the plug-in’s execution.

The plug-in saves previous assessment information about each Eclipse project. Instead of using the configuration dialogs, a user may resubmit an assessment in one of three ways: 1. Have a file from the project open in the editor and click the SWAMP button 2. Right-click on the project on Package Explorer and click "Assess Project on SWAMP" 3. Have a file from the project open and select "Resubmit Previous Assessment" from either the dropdown menu or the SWAMP menu in the main menubar

Right Click Submission

4. View assessment results

This plug-in comes with a new perspective named "SWAMP." When a user opens the SWAMP perspective (by clicking on the "Open Perspective" button in the top right corner and selecting the perspective), he or she will see an editor and four views: the package explorer, the weakness table view, the assessment status view, and the weakness detail view.

SWAMP Perspective

4.1. viewing assessment status

The assessment status view shows the status of submitted assessments. The statuses are periodically updated automatically, but the user may click the "Refresh" button any time to query the SWAMP for unfinished assessments' statuses. By right-clicking and selecting "Remove Assessment" on an unfinished assessment, the status of that assessment will no longer appear in the view. Selecting "Remove Assessment" on a finished assessment, will both remove that status row and stop the results from showing on top of the source code in the Eclipse editor.

4.2. viewing results

To view results for a finished assessment, the user must open the source code for the Eclipse project that was assessed. If any weaknesses were found on the currently opened source file, they will show up with annotated markers on the editor and listed in the weakness table view. Single-clicking any weakness in the table view will show more detailed information about the weakness in the weakness detail view. Double-clicking any weakness in the table view, will jump the user to that weakness’es location in the source file.

SWAMP Results

5. Troubleshooting

Users can report issues at this project’s GitHub issues page. To gather additional debugging information, a user can click "Installation Details" in the Eclipse toolbar’s Help menu, select the "Configuration" tab, and click the "View Error Log" button.

Appendix A: SWAMP account setup

A user must have a SWAMP account to use this plug-in. To set up an account, follow the instructions at

Appendix B: Eclipse Installation

This plugin requires Eclipse Neon (4.6) or later to run. To install Eclipse, select either Eclipse IDE for Java EE Developers or Eclipse IDE for Java Developers from


This plug-in allows Java and C/C++ Eclipse users to perform static code assessments in the SWAMP and to view the results within the Eclipse Integrated Development Environment. The plug-in can also be found in the Eclipse Marketplace as SWAMP Eclipse Plug-in.




No packages published

Contributors 4