Terms

Last updated 25 September 2026

Marketplace apps · Licensing

Eriksen Labs apps distributed through the Atlassian Marketplace are licensed under the Bonterms Standard End User Agreement, adopted through the Marketplace.

We use a standard agreement deliberately. It is a recognised set of terms that most legal teams have already reviewed, so adopting our apps does not require reading a bespoke contract first. Purchase, renewal, billing and refunds are handled by Atlassian under the Atlassian Marketplace Terms of Use.

Marketplace apps · Provider-specific terms

The following apply in addition to the Bonterms Standard End User Agreement.

1. Support. Support is provided through the Eriksen Labs support portal and by email at support@eriksenlabs.com during Norwegian business hours. Response targets by severity are published in our service level agreement.

2. Availability. Eriksen Labs apps run entirely within Atlassian infrastructure. Eriksen Labs operates no servers of its own and makes no separate uptime commitment; app availability follows the availability of the customer's Atlassian site.

3. Third-party components. Mermaid Diagrams & Gantt renders diagrams using Mermaid and CodeMirror, open-source libraries distributed under the MIT licence. Recurring Requests and Issue Templates & Create Defaults use Atlassian's own Forge packages and React, an open-source library distributed under the MIT licence.

4. Customer data. What an app can access differs by app, and is shown on its install screen before installation.

Mermaid Diagrams & Gantt requests no Atlassian permission scopes. Diagram content is rendered in the customer's browser and stored by Atlassian within the customer's own Confluence instance.

Recurring Requests asks for the permission scopes shown on its install screen, and stores schedules, templates, the details of the requests being repeated, and per-project settings in Forge storage within the customer's own Atlassian instance. This includes personal data, as described in the privacy policy.

Issue Templates & Create Defaults asks for the permission scopes shown on its install screen. It stores templates, their earlier versions, usage counts and the daily check's settings and findings in Forge storage within the customer's own Atlassian instance, and keeps its Create dialog settings in the customer's own Jira site. It records nothing about the people who use it; templates hold whatever the customer's administrators write or copy from an issue, as described in the privacy policy.

In each case the data remains inside Atlassian's infrastructure. Eriksen Labs operates no servers that receive it and has no means of accessing it.

5. Data processing. Where an app processes personal data on the customer's behalf, our Data Processing Addendum applies and forms part of these terms.

what it does · Licensing

All of it is free software. The what-it-does command line tool and the GitHub Action that runs it on pull requests are both published under the MIT licence, whose text travels with the package and sits at the root of the repository. You may use either for anything, including commercially, on any repository, and nothing on this page narrows that. Versions already published cannot be unpublished from your machine.

A paid tier for private repositories existed between 8 August and 22 September 2026 and was withdrawn. No purchase was ever made under it. If you believe you were charged, write to support@eriksenlabs.com and it will be refunded in full.

what it does · What it does not promise

The scanner reads code without running it. It cannot see a path chosen at runtime, and the absence of a finding is not proof that nothing is wrong. Every report says so on its own front page rather than in a footnote here. It is a tool for noticing things worth checking, not an audit, a security certification, or a guarantee about your software.

Findings can be wrong. A check may live behind an import the scanner could not follow, and where that is possible the report says which import blinded it. Nothing in this product should be actioned without a person looking.

The Action fails open by design. If a scan errors, the check passes and says so in the log. The only failure it produces over a finding is one you asked for by setting fail-on-new.

To the extent permitted by law, our total liability under these terms is limited to the amount you paid us in the twelve months before the claim. For the free scanner and pull request check, which you paid nothing for, that amount is nothing — the MIT licence's warranty disclaimer applies and is the whole of it.

Support

Support is provided through our support portal and by email at support@eriksenlabs.com. We aim to respond to all requests within two business days.

Support covers installation, configuration, defect reports and questions about intended behaviour. It does not include authoring content on your behalf, support for Atlassian products themselves, or interpreting what a scanner finding means for your particular application.

Trademarks

Atlassian, Jira and Confluence are trademarks of Atlassian Pty Ltd. Eriksen Labs is an independent Atlassian Marketplace Partner, and is not affiliated with or endorsed by Atlassian.