a6256705e5
The `plane.authentication` logger runs at INFO in production with a JSON formatter that serialises `extra` fields, so anything handed to these log calls is written to the production log stream verbatim. `OauthAdapter.get_user_response()` logged the outgoing request headers on failure, and those headers carry the provider access token as a bearer credential — a live token in clear text. It also had no diagnostic value: the dict has the same shape on every call. Replaced with the provider name and the response status code, which say which IdP failed and how (401 token rejected, 403 scope/rate limit, 404 wrong userinfo URL, None connection error). `Adapter.sanitize_email()` interpolated the rejected address into the log message. It was the only f-string logger call in the package; every sibling logs a constant string and confines the email to the exception payload, which is left untouched, so the caller still receives the address. `GitHubOAuthProvider.set_user_data()` logged the resolved email at DEBUG. That record cannot be emitted today — the console handler is pinned to INFO — but it would start leaking PII the moment a DEBUG handler was attached. The three providers now read their client secret in a call of its own rather than batching it with their non-secret settings. `get_configuration_value()` returns every requested value in one tuple, which makes the secret indistinguishable from the values beside it to anything tracking where it flows; GITEA_HOST and GITLAB_HOST build `userinfo_url`, so the shared tuple marked every response fetched with that URL as secret-derived. Splitting the reads keeps `user_login` — a public GitHub handle and the only per-event signal on the not-in-org line — instead of deleting real audit data to satisfy a false positive. The split is structural only: values resolve by key, in request order, exactly as before. Closes the three open py/clear-text-logging-sensitive-data CodeQL alerts.
Modern project management for all teams
Website • Forum • X • Documentation
Meet Plane, an open-source project management tool to track issues, run sprints cycles, and manage product roadmaps without the chaos of managing the tool itself. 🧘♀️
Plane is evolving every day. Your suggestions, ideas, and reported bugs help us immensely. Do not hesitate to join in the conversation on Forum or raise a GitHub issue. We read everything and respond to most.
🚀 Installation
Getting started with Plane is simple. Choose the setup that works best for you:
-
Plane Cloud Sign up for a free account on Plane Cloud—it's the fastest way to get up and running without worrying about infrastructure.
-
Self-host Plane Prefer full control over your data and infrastructure? Install and run Plane on your own servers. Follow our detailed deployment guides to get started.
| Installation methods | Docs link |
|---|---|
| Docker |  |
| Kubernetes |  |
Instance admins can configure instance settings with God mode.
🌟 Features
-
Work Items Efficiently create and manage tasks with a robust rich text editor that supports file uploads. Enhance organization and tracking by adding sub-properties and referencing related issues.
-
Cycles Maintain your team’s momentum with Cycles. Track progress effortlessly using burn-down charts and other insightful tools.
-
Modules Simplify complex projects by dividing them into smaller, manageable modules.
-
Views Customize your workflow by creating filters to display only the most relevant issues. Save and share these views with ease.
-
Pages Capture and organize ideas using Plane Pages, complete with AI capabilities and a rich text editor. Format text, insert images, add hyperlinks, or convert your notes into actionable items.
-
Analytics Access real-time insights across all your Plane data. Visualize trends, remove blockers, and keep your projects moving forward.
🛠️ Local development
See CONTRIBUTING
⚙️ Built with
📸 Screenshots
📝 Documentation
Explore Plane's product documentation and developer documentation to learn about features, setup, and usage.
❤️ Community
Join the Plane community on GitHub Discussions and our Forum. We follow a Code of conduct in all our community channels.
Feel free to ask questions, report bugs, participate in discussions, share ideas, request features, or showcase your projects. We’d love to hear from you!
🛡️ Security
If you discover a security vulnerability in Plane, please report it responsibly instead of opening a public issue. We take all legitimate reports seriously and will investigate them promptly. See Security policy for more info.
To disclose any security issues, please email us at security@plane.so.
🤝 Contributing
There are many ways you can contribute to Plane:
- Report bugs or submit feature requests.
- Review the documentation and submit pull requests to improve it—whether it's fixing typos or adding new content.
- Talk or write about Plane or any other ecosystem integration and let us know!
- Show your support by upvoting popular feature requests.
Please read CONTRIBUTING.md for details on the process for submitting pull requests to us.
Repo activity
We couldn't have done this without you.
License
This project is licensed under the GNU Affero General Public License v3.0.