Super Productivity
super-productivity.comPrivacy-respecting, open-source task manager and time tracker. All data is stored locally on your device - no account required, no cloud dependency, and zero telemetry. Supports Jira, GitLab, GitHub, Gitea, OpenProject and CalDAV integration. Features include time tracking, Pomodoro timer, break reminders, and idle detection.
Super Productivity Source Code
Author
Description
Super Productivity is an advanced todo list app with integrated Timeboxing and time tracking capabilities. It also comes with integrations for Jira, GitLab, GitHub and Open Project.
Homepage
http://super-productivity.com?ref=githubRepository
- LicenseMIT
- Created06 Jan 17
- Primary languageTypeScript
- Size188,696 KB
- Stars23,597
- Forks2,284
- Watchers23,597
Top Contributors
@johannesjo (19794)
@dependabot[bot] (650)
@steindvart (155)
@bytrangle (111)
@cocojojo5213 (80)
@jiongxuan (70)
@novikov1337danil (68)
@MostafaAmin07 (62)
@zenoprax (50)
@tiliakoos (40)
@Cyber-Syntax (38)
@kiausch (37)
@overcuriousity (35)
@stkofler (35)
@costajohnt (32)
@hugaleno (31)
@davidvornholt (28)
@claude (27)
@nonameformr (27)
@aakhter (26)
@hajiboy95 (25)
@lrq3000 (23)
@milotype (23)
@thetric (22)
@loviuz (22)
@Ronaldo93 (21)
@theBenForce (19)
@miqh (18)
@zoli (18)
@symonbaikov (17)
@panoramix360 (16)
@kkoyung (15)
@Abrar74774 (14)
@jpeterburs (14)
@lucadallavalle (14)
@siemieniuk (14)
@wilbowma (14)
@consultorseovalencia (13)
@symdec (13)
@MarkQuach12 (13)
@GabeSilvaDev (13)
@Hetsavani (13)
@berhram (13)
@janLo (13)
@kwongtn (13)
@notsecret808 (12)
@MannXo (12)
@KamilDev (12)
@BadBossy (12)
@Zoriot (12)
@ebbbang (11)
@blyedev (11)
@alosarjos (11)
@gotjoshua (11)
@Mustache-Games (11)
@qievenz (11)
@Garrett04 (10)
@forge34 (10)
@kerkenit (10)
@lanesawyer (9)
@sespiros (9)
@djanilson-barista (9)
@aripollak (8)
@penn5 (8)
@bugixtix (8)
@Jackymancs4 (8)
@cbergmann (8)
@Vedant817 (8)
@OptionalLion411 (8)
@SilverGreen93 (8)
@makomi (7)
@MParvin (7)
@mhmmdhandika (7)
@NoobFullStack (7)
@RayBB (7)
@lntutor (7)
@baflo (7)
@ba6ul (7)
@Morganamilo (7)
@LordJABA (6)
@mycochang (6)
@BigWebstas (6)
@PannenetsF (6)
@Heapnotizer (6)
@Droyder7 (6)
@Fleker (6)
@nskins (6)
@H1manshu01 (6)
@Copilot (5)
@sanchpet (5)
@TypicalUsername-ai (5)
@iwilltry42 (5)
@stavby (5)
@ReduxST (5)
@maxliesegang (5)
@ExoGitH (5)
@davidrr21 (5)
@uinstinct (4)
@sriram15 (4)
@ryziopl (4)
Recent Commits
Johannes Millan(11 Nov 26)
feat(sync): name failed ops in the log and triage fuzz findings (#11701) * feat(sync): name ops that failed to apply in the exported log * test(sync): triage fuzz findings and run them over file sync * test(sync): pin the note order stop after a lost note conflict * docs(sync): name the renamed conflict answer in the fuzz harness * test(sync): pin the force-upload skip trace as a regression * ci(lighthouse): raise script and total count budgets by 5 The startup trim in 2ea16f550c went to master without a Lighthouse run. It cut 197 kB from the initial bundle but split it into four more scripts, so every PR now fails the count budget with 257 scripts and 337 requests. * ci(lighthouse): raise count budgets to 270 scripts and 350 requests Master gained four more scripts an hour after the last bump (focus-mode iOS effects, planner deadline card), again without a Lighthouse run: CI now counts 261 scripts and 341 requests. Leave room for nine more.
Johannes Millan(11 Nov 26)
feat(task-repeat): turn one future occurrence into a normal task (#11700) * feat(task-repeat): turn one future occurrence into a normal task Adds "Separate task for <date>" next to "Skip for date" in the dialog opened from a repeat projection. It skips that date in the series and adds a normal task for the day, with no repeatCfgId and a random id. The skip is written first, as updateTaskRepeatCfg with the new deletedInstanceDates, then addTask. A field update rather than deleteTaskRepeatCfgInstance: conflict resolution cannot read that op's change, so a concurrent rule edit or cursor update would replace the whole series and drop the skip. No new action type, persisted field or schema bump. The creation cursor is not touched. Hidden for series that repeat from the completion date. Fixes #11694 * ci(lighthouse): raise resource count budget for deferred chunks 2ea16f550c moved the tag filter chip input (Material chips and autocomplete) out of the initial bundle and loads it on idle at every start. That is 4 more script requests in the Lighthouse run: 253 before, 257 after, against a budget of 255, so every PR with code changes fails "PWA & Lighthouse" (also seen on #11592). Raise the script count budget from 255 to 260 and the total count from 335 to 340 (measured: 257 scripts, 337-338 total). * docs(wiki): mention the separate-task action for projections * ci(lighthouse): raise count budgets to 270 scripts and 350 requests Master gained four more startup scripts after the last bump (commits 1a7c90966c and a904bb71b1): CI now counts 261 scripts and 341 requests, on this PR and on another PR merged into the same master. Same values as the bump on feat/make-a-plan-to-get-sync-to-work-941cb1, so the two PRs do not conflict.
Johannes Millan(11 Nov 26)
docs(sync): record the version-spread and quota readings (#11704) Adds the 2026-11-11 production readings to the fleet-boundary plan: 18.3% of devices active in 30 days are older than v19.2.0 (threshold: under 5%), and 8 of 16,136 accounts are above half of their quota. No floor, gate or checkpoints follow from them. Co-Authored-By: Claude Fable 5.2 <[email protected]> Claude-Session: https://claude.ai/code/session_01Rqkmg7Ud1rm7NQg3bP5xsf
Johannes Millan(11 Nov 26)
feat(tracking-presence): ring play button while another device tracks The header pill is hidden below 600px, so phones only saw remote tracking in the Android widget/notification. The play button now gets a dashed accent ring and a devices badge while another device actively tracks; its tooltip names the device and that starting here takes over.
Johannes Millan(10 Nov 26)
feat(focus-mode): notify on iOS when a session ends in background Part of #8398
Johannes Millan(10 Nov 26)
feat(planner): open the task from a deadline card A deadline card in the Planner only opened the deadline dialog, so a task with a deadline but no planned date could not be edited there (2026 user survey). A click now opens the task like other Planner cards; the deadline is edited from the task. The card is also reachable with Tab and opens with Enter. No E2E covered the old click, so none changed. Related to #10853 (dragging a deadline card to plan work), which stays open: the survey ask was editing, not dragging.
Johannes Millan(10 Nov 26)
docs(wiki): add planning how-tos for planner, schedule, repeats
Johannes Millan(10 Nov 26)
docs(plans): record decisions on survey feature gaps
Johannes Millan(11 Nov 26)
docs(sync): plan for bounding the released fleet per transport (#11697) Adds docs/plans/2026-11-10-sync-fleet-boundary.md: an evaluation of a SuperSync version floor, client checkpoints and a file-format generation, with the maintainer's decisions (F1-F9), missing evidence, and a progress log covering the REPAIR divergence fix (#11688) and the parked v3 default (#11684). Co-Authored-By: Claude Fable 5.2 <[email protected]> Claude-Session: https://claude.ai/code/session_01Rqkmg7Ud1rm7NQg3bP5xsf
Johannes Millan(11 Nov 26)
test(e2e): cover two devices seeding one empty v3 folder (#11691) v3 counterpart of #10459's race, which webdav-late-snapshot.spec.ts pins for v2. A fresh device's first write is held until another device has seeded the folder, by a first upload or by a folder move (the server-migration path). Both devices sync again and a third, empty device joins. No device may drop its own task without being asked, and the server and the new device must keep the seeder's task. Today the fresh device's create-only claim of sync-data.json loses to the seeder's tombstone, so it asks instead of overwriting. Claude-Session: https://claude.ai/code/session_01Rqkmg7dbWynf9vnWXD6zsC Co-authored-by: Claude <[email protected]>
Johannes Millan(10 Nov 26)
test(sync): shrink slow file-snapshot control spec to avoid timeout
Johannes Millan(10 Nov 26)
feat(history): link archive snackbars to History After archiving completed tasks, the confirmation snack offers a History action so users can find and restore them. Clarify the finish-day tooltip and the wiki restore steps.
Johannes Millan(10 Nov 26)
docs(agents): note supersync:latest waits for green sync suites Changes agent behaviour: when judging whether a master commit has reached self-hosters, agents no longer assume `supersync:latest` moves with every master push. It is published only after the server tests and the SuperSync E2E shards pass for that commit.
Johannes Millan(10 Nov 26)
ci(supersync): gate latest on SuperSync E2E shards only The image gate called the whole sync E2E workflow. Over the newest 32 master runs that was red 9 times, 6 of them from test defects in the released-client job, so `latest` would often stay stale for reasons unrelated to the server. e2e-scheduled.yml gets a workflow_call input `supersync_only`; the publisher passes it, so the gate runs the build and the SuperSync shards. WebDAV, released clients and the duplicate server unit job are skipped there. Schedule, push and dispatch runs are unchanged.
Johannes Millan(10 Nov 26)
ci(supersync): publish latest only after green sync suites A master push that changes the image inputs now runs the SuperSync server tests and the sync E2E workflow as reusable workflows in the publisher run. `latest` and `master-<sha>` are built only if both pass for that commit; a failed, cancelled or skipped suite publishes nothing. A master workflow_dispatch without release_tag still builds at once (existing manual override). Release images (`vX.Y.Z`) are unchanged and not gated. Play internal and Snap edge are untouched.
Johannes Millan(10 Nov 26)
perf(startup): trim 197 kB from the initial bundle - Drop the unused chart theme sync: it imported ng2-charts and with it chart.js (~200 kB) on every boot, although no chart uses ng2-charts. Remove the ng2-charts dependency. - Load the issue provider dialog only when the calendar "Connect" snack action is used, and the tag filter chip input on idle. - Build the emoji Intl.Segmenter on first use and skip segmentation for ASCII-only strings such as Material icon names. Initial JS 5,096 kB -> 4,899 kB. First render about 1-2% faster in an interleaved A/B, so real but not noticeable on its own.
Johannes Millan(10 Nov 26)
docs(wiki): note per-device plugin installs, add all-tasks view how-to
Johannes Millan(11 Nov 26)
fix(supersync): keep sending retained ops before a causal REPAIR (#11688) A device that holds unsynced edits drops an incoming causal REPAIR, on the grounds that it already applied every op the repair was built from. The download path skipped any cursor behind the latest full-state op straight to that op, so a device behind the REPAIR never got those ops and stayed diverged. The skip is no longer applied when the latest causal full-state op is a REPAIR, the device has synced before, the REPAIR is at most 10,000 ops ahead, the ops in between are retained, and no other full-state op lies in between. Imports and new devices keep the skip. The sync-fuzz fake server mirrors the rule. Not covered: a pruned prefix, another full-state op in between, a REPAIR further ahead than the cap, and older self-hosted servers. Co-Authored-By: Claude Fable 5.2 <[email protected]> Claude-Session: https://claude.ai/code/session_01Rqkmg7Ud1rm7NQg3bP5xsf
Johannes Millan(11 Nov 26)
test(sync): add a second project and task moves to the sync fuzz harness (#11683) * docs(sync): evaluate extending the sync fuzz harness and gating on it Plan note only: no production code, workflow or harness change. Co-Authored-By: Claude Fable 5.2 <[email protected]> Claude-Session: https://claude.ai/code/session_01Rqkmg4YUMy2P2S8EPAqXin * docs(sync): record the fresh-context review of the fuzz evaluation Adds a task-reorder candidate, corrects the file-port estimate and the sampled-fix verdicts, and narrows the gating wording. Co-Authored-By: Claude Fable 5.2 <[email protected]> Claude-Session: https://claude.ai/code/session_01Rqkmg4YUMy2P2S8EPAqXin * test(sync): add a second project and task moves to the sync fuzz harness A new mix `move` crosses task edits, tracking, adds and deletes with moves between three projects. Its two extra projects are created only in a run that moves tasks, and the generator draws the target inside its own case, so the other mixes' traces, the 60 existing pins and the 120-seed baseline are unchanged (compare: 0 newly failing, 120 of 120 seeds with identical steps). - ledger: task.projectId; a move is a whole-entity side, as moveToOtherProject carries the flat pre-move task - oracle: each project lists exactly its own top-level tasks (move runs only) - sync-fuzz:compare leaves a mix the base lacks out of the comparison and reports it - nine pins: one coverage trace and eight minimal traces of the mix's failure classes, each failing 3 of 3 replays; untriaged, no fix here Test infrastructure only: no production code changes. The plan note records the maintainer's decisions (M1-M5) and the slice's results. Co-Authored-By: Claude Fable 5.2 <[email protected]> Claude-Session: https://claude.ai/code/session_01Rqkmg4YUMy2P2S8EPAqXin * test(sync): keep move pins from hiding other mixes' signatures in the fuzz sweep Review of the task-move slice, test infrastructure only: - sync-fuzz-seeds.benchmark.ts: a pin that moves a task explains only a run that moves one. Three move pins have a generic primary (time-loss, REPAIR, lost-entity), which no earlier pin had, so the random sweep would have stopped reporting those signatures in every mix. - sync-fuzz-compare.js: fail when the base's mixes cannot be read instead of counting every mix as new and comparing nothing. - oracle spec: negative controls for membership:listed-twice and for the membership oracle staying off in a run without a move. - restore checkTodayNotes' doc comment, describe "untriaged" pin refs in the pinned spec's header, correct the suite count in the plan. Co-Authored-By: Claude Fable 5.2 <[email protected]> Claude-Session: https://claude.ai/code/session_01Rqkmg4YUMy2P2S8EPAqXin --------- Co-authored-by: Claude <[email protected]>
Johannes Millan(11 Nov 26)
test(super-sync-server): pin unique, gap-free server_seq under concurrent uploads (#11682) The legacy multi-client suite deleted in #11676 was the only test of simultaneous uploads. This real-PostgreSQL spec fires 8 clients' uploads at one account at once, retries the batches rejected as retryable serialization conflicts (as a client would), and asserts 40 rows with server_seq 1..40, each acknowledged sequence matching its stored row, and last_seq = 40: a rejected batch stores nothing and leaves no gap. Locally each run saw ~28 serialization conflicts, so the lock really contends. With the lock, RepeatableRead, the atomic increment and the unique (user_id, server_seq) index all removed, it fails with duplicate sequences. Added to test:integration:postgres (and excluded from the mocked unit run). Claude-Session: https://claude.ai/code/session_01Rqkmg7dbWynf9vnWXD6zsC Co-authored-by: Claude <[email protected]>
Johannes Millan(11 Nov 26)
chore(sync): drop dead excluded server tests, stale docs and unused exports (#11676) * chore(sync): drop dead excluded server tests, stale docs and unused exports No sync logic changes. - super-sync-server: delete the seven test files vitest.config.ts has excluded since 2025-12-21 (written for the removed SQLite/password-login implementation; 115 of 140 failed when run alone) and their exclude entries. Their live scenarios are covered by current suites or obsolete; remaining gaps are listed in the follow-up report, not ported. - docs: the contributor decision table and sync-architecture.html still told contributors to yield after a dispatch loop, contradicting sync rule 6 (#10441); describe no-multi-entity-effect as the error eslint.config.js configures; fix the "two of the three" count under the five-row table. - Remove 17 exports with no reference in src, packages, electron, e2e or tools, plus the declarations that only fed them (AppMainFileNoRevsData, LocalSyncMetaForProvider, DOWNLOAD_RETRY_BASE_DELAY_MS, the unused RETRY_DELAY_BASE_MS token). The download-retry, rejected-ops-warning and state-size-warning constants documented behaviour that does not exist. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Rqkmg7dbWynf9vnWXD6zsC * test(super-sync-server): cover live gaps left by the deleted legacy suites The legacy route/auth suites deleted in 052bed985f were the only tests of a few live behaviours. Add focused tests (no production change): - every /api/sync/* route rejects a missing or invalid token (the authenticate preHandler wiring; middleware.spec covers the hook itself) - GET /ops asks for limit+1, reports hasMore, defaults to 500, refuses >1000 and a missing cursor - verifyEmail rejects unknown and expired tokens (user and pending-passkey paths) and clears a token on use; new tokens live 24 hours - verifyToken rejects a deleted account and malformed or foreign-signed JWTs Each test was checked to fail when the behaviour it pins is broken. Concurrent uploads getting unique serverSeq still needs real Postgres and stays a gap. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Rqkmg7dbWynf9vnWXD6zsC * test(super-sync-server): name two verification tests by what they pin Review follow-up: the 24-hour expiry test name did not read, and the one-time-use test pins the compare-and-set update rather than real state. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Rqkmg7dbWynf9vnWXD6zsC --------- Co-authored-by: Claude <[email protected]>
Johannes Millan(11 Nov 26)
fix(sync): advance stored clock when appending force-upload import (#11681) * test(sync): reproduce skipped op after force overwrite Three WebDAV devices: the first change a device makes after Force Overwrite never reaches a device that applied the import and then another device's op. Fails until the fix for #11651 lands. * fix(sync): advance stored clock when appending force-upload import ServerMigrationService appended its SYNC_IMPORT with a plain append, which writes the op but not the stored vector clock. The device's next op then reused the import's clock, and a peer that had applied the import and since learned anything newer judged that op superseded and skipped it for good. Append through appendMixedSourceBatchSkipDuplicates, which rebases on the durable clock and advances it in the same transaction. Fixes #11651 * test(sync): cover stored clock advance for local full-state op
Johannes Millan(11 Nov 26)
ci(e2e): run the scheduled WebDAV suite in both v2 and v3 formats (#11677) * ci(e2e): run the scheduled WebDAV suite in both v2 and v3 formats Scheduled and push runs only exercised the v2 file format, while v3 is the format decided as long-term (#10339 reverted only its empty-folder default). The WebDAV job is now a matrix over the format: schedule and push run v2 and v3; a manual run uses the chosen `webdav_format`, which gains a `both` option. Failure artifacts carry the format so the two legs do not collide. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Rqkmg7dbWynf9vnWXD6zsC * test(e2e): pin the late-snapshot WebDAV spec to the v2 format webdav-late-snapshot.spec.ts guards #10459, a v2-only race, but inherited E2E_WEBDAV_FORMAT. On the new v3 leg of the scheduled WebDAV job its seed was written as v3, so `expect(seeded.version).toBe(2)` failed and the server-migration prompt never appeared (run 42922923627). Pin the format; a v3 counterpart of the race, if one exists, needs its own spec. Co-Authored-By: Claude Opus 5.5 <[email protected]> Claude-Session: https://claude.ai/code/session_01Rqkmg7dbWynf9vnWXD6zsC --------- Co-authored-by: Claude <[email protected]>
Johannes Millan(11 Nov 26)
feat(super-sync-server): add a read-only quota headroom report (#11675) `npm run monitor -- quota` shows how close accounts are to their storage quota. The server prunes history only behind a full-state boundary and routine sync creates none, so the counter mostly only grows. - Fleet: accounts above 50, 75 and 90 percent of their own quota and at or over it, from the users counters (every account, no operations access). - Growth: for accounts with a device heartbeat in the last 30 days, highest quota use first and capped at MONITOR_SCOPE_USERS, the bytes uploaded in the window (one index range per account) and the projected time to quota, plus counts reaching it within 90, 180 and 365 days. - Accounts appear by numeric id only; the report never reads email. Tests run the projection math and the SQL on PGlite; no real database. Claude-Session: https://claude.ai/code/session_01Rqkmg7dbWynf9vnWXD6zsC Co-authored-by: Claude <[email protected]>
Johannes Millan(11 Nov 26)
docs(sync): note the older-write-won re-run on 954256d (#11674) The residue table recorded 5 older-write-won seeds on 1620939; the report on 954256d shows 10. A sync-fuzz:compare against 1620939 shows identical steps and final values for the 6 new seeds: #10498's oracle reclassified existing field losses. Record that beside the historical table instead of rewriting it. Claude-Session: https://claude.ai/code/session_01Rqkmg7dbWynf9vnWXD6zsC Co-authored-by: Claude <[email protected]>
Johannes Millan(11 Nov 26)
fix(sync): keep a SuperSync snapshot pending when its upload fails without a server verdict (#11673) A full-state upload that threw (rejected token, a proxy's 404/413/52x, an HTML or malformed 2xx body, missing credentials) was reported as the server rejecting the op. A rejected full-state op blocks every later upload, and a rejected server-migration snapshot is never created again, so one environmental failure stopped uploads for good. SuperSync judges a snapshot in the reply body, with a structured errorCode on a non-2xx reply, or with a bare HTTP 400. Any other thrown error is now re-thrown: the op stays pending and the error reaches the user (auth errors reach the re-login handling). Errors with an errorCode, the legacy SYNC_IMPORT_EXISTS message, ClientUpdateRequiredSPError and retryable errors behave as before. File-based sync is unchanged. Adds an E2E reproduction (401 and proxy 413 on the snapshot route) that fails on master and passes with the fix. Follow-ups: #11671, #11672. Co-Authored-By: Claude Fable 5.2 <[email protected]> Claude-Session: https://claude.ai/code/session_01Rqkmg78M7U3EwrGxUGhYZC
Johannes Millan(10 Nov 26)
feat(tasks): hint that attachments stay on one repeating instance (#11663) Attachments are not part of the repeat config, so one added to an instance never reaches the next. Say so in the add-attachment dialog, only while adding to a task with a repeatCfgId, and point to the config's Default notes for links that should carry over. No model, sync or settings change. Context: #10706, #8745 (not resolved by this).
Johannes Millan(10 Nov 26)
fix(sync): encode WebDAV Basic auth credentials as UTF-8 (#11658) * test(sync): reproduce WebDAV auth failure with non-ASCII password * fix(sync): encode WebDAV Basic auth credentials as UTF-8 btoa on the raw "user:password" string threw for characters above U+00FF (e.g. €) and sent é/ß as single Latin-1 bytes, which servers that hash the password as typed (Nextcloud, Apache) answer with 401. Encode as UTF-8 first (RFC 7617), in one helper used by the sync requests, the connection test and the Nextcloud user-id lookup. Compatibility: a password with only U+0080-U+00FF characters that works today against a server decoding Basic credentials as ISO-8859-1 (Tomcat/Jetty defaults) will get 401 and must be re-set.
Johannes Millan(10 Nov 26)
test(tools): send electron-builder logs to stderr in appx config test (#11665) getConfig logs "loaded configuration" to stdout. Under `node --test` the child's stdout carries the runner's serialized messages, and Node 22's parser tries to deserialize plain text that arrives in the same chunk right after a message, failing the file with "Unable to deserialize cloned data due to invalid or unsupported version" (build run 42880293974, linux lint step). Locally 3 of 60 runs failed before, 0 of 150 after. Point the builder-util logger at stderr, which the runner reads as lines. Claude-Session: https://claude.ai/code/session_01Rqkmg7BxQn3knodx4iDoVo Co-authored-by: Claude <[email protected]>
Johannes Millan(10 Nov 26)
fix(sync): make sync error messages say what to do next (#11653)
Super Productivity Security
Security Advisories (2)
- mediumPatched
CVE-2026-102539SuperSync E2EE setup uploads and stores all user operations in plaintext before password is set
- highPatchedCVSS 7.8
CVE-2026-71551Arbitrary OS Command Execution via IPC EXEC Handler with Persistent Whitelist
Super Productivity Website
Website
Super Productivity – Open-Source Deep Work Task Manager
Free, open-source, privacy-first task manager with built-in time tracking, timeboxing, and focus mode. Works offline, no account required, developer-friendly.
Redirects
Does not redirect
Security Checks
All 65 security checks passed
Server Details
- IP Address89.22.100.24
- Hostnamevps54630.alfahosting-vps.de
- LocationDortmund,Nordrhein-Westfalen,Germany,EU
- ISPdogado GmbH
- ASNAS8648
Associated Countries
DE
Safety Score
Website marked as safe
100%
Trackers
No known trackers found
Blacklist Check
super-productivity.com was found on 0 blacklists
- AntiSocial Blacklist
- Artists Against 419
- Badbitcoin
- Bambenek Consulting
- CERT Polska
- CoinBlockerLists
- CRDF
- CryptoScamDB
- EtherAddressLookup
- EtherScamDB
- Fake Website Buster
- MetaMask EthPhishing
- NABP Not Recommended Sites
- OpenPhish
- PetScams
- PhishFeed
- PhishFort
- Phishing.Database
- PhishStats
- PhishTank
- Phishunt
- RPiList Not Serious
- Scam.Directory
- SecureReload Phishing List
- Spam404
- StopGunScams
- Suspicious Hosting IP
- ThreatFox
- ThreatLog
- TweetFeed
- URLhaus
- ViriBack C2 Tracker
Website Preview
Super Productivity Android App
APK Info
- AppSuper Productivity
- Creation Date11 Jan 25
- Last Updated11 Jan 25
- Current Version11.0.3
- Privacy ReportView on Exodus →
De-Googled Compatibility
Trackers
No trackers found
Permissions
- Access Network State
- Foreground Service
- Internet
- Post Notifications
- Read External Storage
- Write External Storage
- Dynamic Receiver Not Exported Permission
Super Productivity Docker
Container Info
super-productivity
To-do list with timeboxing and time tracking built in, and it can pull in issues from Jira, GitHub and GitLab. Source: https://github.com/super-productivity/super-productivity
View on DockerHub
johannesjo/super-productivity:latestRun Command
docker run -d \ -p 8095:80/tcp \ --restart=unless-stopped \ johannesjo/super-productivity:latest
Compose File
version: 3.8
services:
super-productivity:
image: "johannesjo/super-productivity:latest"
ports:
- "8095:80/tcp"
restart: unless-stoppedPort List
- 8095:80/tcp
Super Productivity Reviews
More Task Management
A Getting Things Done + Pomodoro productivity system for desktop and mobile. Local-first, no account required, can sync via WebDAV/Dropbox/local file or self-hosted deployment. With a CLI, REST API and MCP for scripting, has optional BYOK AI.
Vikunja is an open-source to-do application. It is suitable for a wide variety of projects, supporting List, Gantt, Table and Kanban views to visualize all tasks in different contexts. For collaboration, it has sharing support via private teams or public links. It can be self-hosted or used as a managed service for a small fee.
About the Data: Super Productivity
Change History
- Added #438
Edit Super Productivity Data
You can edit Super Productivity's entry in this section of awesome-privacy.yml by submitting a PR to our GitHub repo.
Note that some of the information shown above has been aggregated from external
sources, a list of these can be found data documentation.
Origin Data
Modify Data
API
You can access Super Productivity's data programmatically via our API. Simply make a GET request to:
https://api.awesome-privacy.xyz/v1/services/super-productivityThe REST API is free, no-auth and CORS-enabled. To learn more, view the API Docs or read the API Usage Guide.
Share Super Productivity
Help your friends compare Task Management, and pick privacy-respecting software and services.
Share Super Productivity and Awesome Privacy with your network!
