Least privilege. Every permission is a read permission, so the gadgets cannot create, change or delete anything in Jira. The list of permissions and the reason for each is in Privacy and data.
Least data egress. The apps run entirely on Atlassian's Forge platform. They declare no external hosts and make no calls outside Atlassian.
No stored data. There is no database and no file storage. Results are computed per request and discarded.
Acting as the viewer. Calls to Jira are made as the person looking at the dashboard, so Jira's own permissions decide what each person sees.
Untrusted input. JQL filters and board and sprint ids typed into the settings are validated (length, balanced parentheses, digits only for ids). Everything that comes back from Jira is escaped before it is put on the screen.
Dependencies. The direct runtime dependencies are Atlassian's Forge packages. npm audit of the whole dependency tree finds no high or critical issues (checked 11 Nov 2026). It reports two moderate advisories, one in glob and one in minimatch; both reach the project through Atlassian's @forge/manifest package, which is why npm lists five packages as affected.
Reporting a vulnerability
Write to security@cooloffapp.com with the app name, the version and the steps to reproduce. Please do not include customer data. A report is acknowledged within 3 business days. Confirmed vulnerabilities are handled under the Atlassian Marketplace Security Bug Fix Policy.
If something goes wrong
Investigate. Find the cause from the logs and the code, decide whether any end-user data could be affected (the apps keep none; the support mailbox is the only store), and which versions are involved.
Tell Atlassian. Promptly and within 24 hours, by raising a P1 ticket as Atlassian's incident guidelines ask, and keep it updated at least every 6 hours while the incident is open.
Contain it. Hide or delist the app, and release a version that turns the affected feature off while the fix is built.
Fix and release. Under the Marketplace Security Bug Fix Policy a critical vulnerability in a cloud app is fixed within 10 days and a high one within 4 weeks of being reported or triaged.
Tell customers. Without undue delay and within 72 hours of becoming aware, by a notice inside the gadgets and in the Marketplace listing, and by e-mail where the vendor holds a contact. A notice that refers to Atlassian goes out once Atlassian approves it, as the Marketplace Partner Agreement requires; the vendor asks for that approval in the P1 ticket.
Review. Write a short account of the cause, the impact and the fix, and keep it with the release notes.
If an account or the vendor's computer is compromised
Whoever can deploy as the vendor could ship hostile code, so this counts as an incident even when no customer has reported anything.
Cut access. Revoke the Forge and GitHub tokens, sign out every session, change the passwords of the Atlassian, GitHub and e-mail accounts, and turn on two-step verification where it is off.
Look. Read each app's deployment list in the Developer Console and compare it with the releases the vendor made; read the repository history for commits the vendor did not make.
Restore. Redeploy each app from a known good commit.
Tell Atlassian and customers. Raise the P1 ticket and follow steps 2, 5 and 6 above.
Vendor controls
Source code is kept in a private repository.
The apps hold no secrets and no customer credentials, so there is nothing of that kind to rotate or leak.