HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Noovolari
leapp
TypeScript2020–2024
Noovolari / leapp

leapp

Leapp is the DevTool to access your cloud

Command LineMobile & DesktopDevOps & Cloud
Explore on GitHubRead Hacker News discussions
3Distinct people
16Mentions
1Explicit recommenders
1.8KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Leapp is the DevTool to access your cloud

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

At the moment I'm struggling with my founder role and accountabilities inside the project. I've switched from a DevOps position to become the Product Owner, managing the…

andreacavagna used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year16 dated mentions

Observed mentions: 2020-12-21 15:13:34 UTC to 2024-03-04 11:04:51 UTC.

024682020-01-01 00:00:00 UTC to 2021-01-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments20202021-01-01 00:00:00 UTC to 2022-01-01 00:00:00 UTC (exclusive): 8 mentions; 2 submissions, 6 comments2022-01-01 00:00:00 UTC to 2023-01-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments20222023-01-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2024-01-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20202020-01-01 00:00:00 UTC2021-01-01 00:00:00 UTC110
20212021-01-01 00:00:00 UTC2022-01-01 00:00:00 UTC826
20222022-01-01 00:00:00 UTC2023-01-01 00:00:00 UTC404
20232023-01-01 00:00:00 UTC2024-01-01 00:00:00 UTC211
20242024-01-01 00:00:00 UTC2025-01-01 00:00:00 UTC101

What Hacker News says

16 sources
andreacavagna·Mar 4, 2024
Location: Turin, Italy Remote: YES Willing to relocate: YES Technologies: TypeScript, AWS, Angular, NodeJS, Python, UX/UI, Marketing, Sales Résumé/CV: https://drive.google.com/file/d/1eac46T_pTcEikWym6YQ599oYtQ5C0_72/view?usp=drive_link Email: a.cava94@gmail.com Summary: Do you find yourself overwhelmed with work, requests, or complaints and in need of assistance to alleviate the pressure, enhance communication, facilitate organization, prioritize tasks, and foster greater trust and transparency? Alternatively, I can work as a full stack developer. AWS Community builder, AWS User group Leader, public speaker (https://www.youtube.com/watch?v=qdu58NAQfU0&t=271s) Or perhaps you need both? =) I have 4+ years of experience as a product manager and 8 in product development (before pm: agile coach, UX designer, and developer). I've be
Read the rest
en the co-founder of the open-core company behind the OSS project Leapp (https://github.com/Noovolari/leapp) Please feel free to reach out.
In Ask HN: Who wants to be hired? (March 2024)
andreacavagna·Mar 29, 2023Submission

Ask HN: Should open source projects track you?

Hello everyone, I'm the maintainer of an open-source DeveloperTool (https://github.com/Noovolari/leapp) With a heuristic of 7000 users daily, I started feeling the need to have more information on how Users are using the project to improve it. Is it the right thing to do to create a better Developer Experience and gain feedback for the end users? On a side: "it's acceptable for open source software not to work is a great thing. This makes it easy for anyone to contribute because there are no hurdles from what your work must include or not include - it's up to you. Mistakes, or half-baked projects included. You can't have innovation without a lot of people being able to contribute and make mistakes, or give up." As pointed out in the PostHog article below, I extracted some important passage: "From a utilitarian perspective, We believe tha
Read the rest
t tracking the minimum data possible to build useful technology, in a way that doesn't share that data with 3rd parties, means that you have the right approach to product analytics in your open source project." In most cases tracking user data to enrich functionalities means you have to deal with an opt-out/opt-in setting (like VSCode does) to get data to the open-source project's maintainers; developers are the most sensitive people regarding data. I've never added this tracking on the Desktop App since I'm worried about the community's reaction. And this is a direct message to them. Is it right to have people helping the growth of the open-source project by tracking only fewer data to improve stability and functionality? "All tracking is bad, many say. We disagree. Done right, it enables more and better software in the world. When it's applied to open source, it often enables more free software for anyone to use." P.S. I'm not yet a user of PostHog, but I want to congrats with them on the article, and the best way (if it is a good thing) to track open-source data is to do it with an open-source project too. All the references are from the below blog post. Great article, guys! => https://posthog.com/blog/open-source-telemetry-ethical
3 points · Open discussion
andreacavagna·Mar 6, 2023
A few suggestion: - start with a password manager (I will suggest https://1password.com). For any service outside the cloud this should be fine - Where possible enable SSO, even for AWS or other cloud services (https://blog.leapp.cloud/how-to-saml-federate-your-aws-accou...). Here an example on how to do it with GSuite and aws - For all your employees I can advice you Leapp as open-source project (https://github.com/Noovolari/leapp). It solve mayor of the problem listed here: . Responsable for the AWS infrastructure get the IAM Security standard on track (short-lived credentials, MFA, IAM Users secured, rotation of credentials and access to the console with a set of secured credentials, and generation of Azure ceredentials) . temporary tokens are mandatory, so let a project like leapp locally manage IAC credentials for you. - Is not too
Read the rest
strictly to manage pipelines only after confirmation? You can create a specific role for managing a specific policy to deploy your pipelines. Here an article on how to start organizing your AWS account as a startup (https://blog.leapp.cloud/aws-multi-account-strategy-explaine...) - "People work on their own devices.": that's why Leapp has been created, check it out. - Optional: "It would be good if developers get credentials to setup small test environments in AWS." how anout creating a sandbox account for them? - "Bonus: How to manage non-technical secrets" even here, Leapp is a desktop app and is vastly used also for accessing to EC2 instances even for not technical people I hope this guide can help you!
In Ask HN: Secure and simple way for secret/credential management in a startup?
dnsmichi·Jan 27, 2022
Thanks for the additional context, helps to understand your situation and resources. > BTW, this is my project (https://github.com/Noovolari/leapp) Looks great. A few suggestions for the first impression opening the project: - Switch to dark mode and verify that the images work in the README and other docs. There is a logo which cannot be seen on the site, it's dark and black. - Focus on telling the "problem to solve" and "why" in the introduction https://github.com/Noovolari/leapp#leapp I initially did not understand the term "cloud access app" - The screenshot description is AWS focussed. https://user-images.githubusercontent.com/9497292/114399348-... If you don't know AWS specifics, it is hard to understand. Think of a more high level catchy architecture overview, or working example. Catch your marketing term with "multiple cloud acces
Read the rest
s strategies". Maybe use a Gif to showcase the key items as done in the one in "key features" - Installation links to a release download page. https://www.leapp.cloud/releases Improve this, highly recommend to create documentation guides for Windows, Linux and macOS, explaining the different commands step-by-step, more tutorial alike. Actually, your website has a docs section, but it is not linked from the GH Readme. Suggest to link to https://docs.leapp.cloud/installation/install-leapp/ instead of the releases page. Here's a PR to fix it: https://github.com/Noovolari/leapp/pull/215 - You are using MkDocs for the documentation. That's amazing <3 - PR template - while fixing the readme, I was confused by the template structure. Maybe get inspired by GitLab MR (similar to PR) templates? Gary Bell wrote a great blog post about them: https://www.garybell.co.uk/merge-request-templates/ - You are using a DCO which requires all commits to be signed off. That's impossible with using the browser to make direct edits to the docs, or otherwise suggestions. It may throw off contributors after their first pull request (it throws me off every time I consider contributing on a mobile device). Did now on my desktop terminal: cd /tmp && git clone https://github.com/dnsmichi/leapp && cd leapp && git checkout patch-1 && git commit --amend -s && git push -f Suggestion: Document the DCO requirement more visible, e.g. with a badge in the README. - The PR fails because because of a check https://github.com/Noovolari/leapp/runs/4971776167?check_sui... "Error: No release type found in pull request title "Update URLs to installation docs in README". Add a prefix to indicate what kind of release this pull request corresponds to (see https://www.conventionalcommits.org/)." That's additional work for contributors. After fixing the DCO sign-off, the next thing to do. Then again, the commit also needs a "docs: " prefix. At this point, I would have lost the desire to contribute. - Why is the contributing.md hidden in the .github directory (https://github.com/Noovolari/leapp/blob/master/.github/CONTR...) and not present in the main repository? I was specifically looking for it at the repository top level when looking to contribute. - https://github.com/Noovolari/leapp/blob/master/.github/CONTR... encourages you with "Please send a GitHub Pull Request to Leapp with a clear list of what you've done (read more about pull requests)." What's a clear list of changes? Suggestions in a new PR: https://github.com/Noovolari/leapp/pull/216 - https://docs.leapp.cloud/contributing/get-involved/ links from the docs to contributing.md As discovered above, contributing.md is more a "things to review" document. It should be the call-to-action document. Or maybe move the content from contributing.md entirely into your documentation - and only link there. I do the same with https://o11y.love/contributing/ for example - Make it easy to spin up a development environment - I don't see any guides to do so? Suggestion: Add Gitpod or a local Docker build and a development.md to your repository. This will be critical for your success to attract contributors. - https://docs.leapp.cloud/contributing/project-structure/ exists but is not linked in contributing.md - Labels help wanted / good first issue are used, but they are not explained/linked in the contributing guide. If you are not familiar with these label types, contributions are harder. Suggestion: Fix this by adding the Call-to-action in your contribution guides. https://github.com/Noovolari/leapp/issues?q=is%3Aissue+is%3A... + https://github.com/Noovolari/leapp/issues?q=is%3Aissue+is%3A... Above are my first impressions starting with the project and trying to find ways to contribute. I did not read the source code yet. I'd suggest addressing them, and then focus on DevRel and marketing ideas. The first impression of a project is crucial to help seed the community plants :)
In Ask HN: Marketing, DevRel and Evangelism working for Open-source
andreacavagna·Jan 27, 2022Recommendation phrase
At the moment I'm struggling with my founder role and accountabilities inside the project. I've switched from a DevOps position to become the Product Owner, managing the delivery of the open-source project and the day to day work, but now I see lack of time in developing a real evangelism and DevRel things inside the Leapp project. I'm completely aware that this is THE crucial part of an open-source project and I really love OSS because of the contributing from all around the world. But is turning that maintain and grow a community around the project, make the project well known, is a full time job for a founder of a project. I still don't know if I have the right skill for that kind of job and where a such particular job can bring me in the future, together with the Noovolari company. BTW, this is my project (https://github.com/Noovolari
Read the rest
/leapp) and I would love to chat more with you!
In Ask HN: Marketing, DevRel and Evangelism working for Open-source
andreacavagna·Jul 1, 2021
We are going to implement a custom credentials process for AWS too with the Leapp Daemon, it's in the roadmap of the project. Thanks for pointing it out. The main difference is that Leapp also disable the profiles whenever they are not needed, so attackers can't find even the credential process attached to a not in use profile. The main idea is to bring only the least credentials needed in order to make developers work. check specification for an in-depth explaination: https://github.com/Noovolari/leapp/wiki/specs
In Show HN: Leapp – Multi-cloud credentials tool for developers
andreacavagna·Jun 30, 2021
Chamber is a wrapper around AWS Session Manager Parameter store. To make Chamber work, you need a set of AWS Credentials. Leapp, by now, manages those AWS credentials and ensure that only short-lived credentials will be stored in the ~/.aws files. Chamber can be a sort of Action of Leapp, like what happens with AWS SSM in Leapp, so for each Leapp Session you can, in the app, access to an EC2 instance directlly from Leapp, without any pem key, via AWS Session Manager System Manager. So the goals of the 2 tools are a bit different, we work to secure and provide access to the Cloud, Leapp is an enabler to work in cloud for developers. If you want to better know what are the goals of the app, refer to the Specification https://github.com/Noovolari/leapp/wiki/specs
In Show HN: Leapp – Multi-cloud credentials tool for developers
andreacavagna·Jun 30, 2021
Less than a year ago, my team and I decided to develop an essential tool that securely manages programmatic (CLI/SDK) access to AWS resources distributed among several Cloud accounts. Temporary credentials access was a constraint for accessing the Cloud in our company, so we decided to build an open-source (https://github.com/Noovolari/leapp) tool for every access method on your behalf. Leapp manages different access methods: IAM Users, IAM Roles federated with multiple Identity Providers (G Suite, Okta, and OneLogin at the time), IAM Role Chained to another AWS entity (the cross-account Role access thing), AWS Single Sign-On Roles, and Azure Subscriptions by now. Leapp store securely information of the developers (like AWS Access Key and Secret Keys) and generate short-lived credentials accessible to any CLI, SKD, and external library. T
Read the rest
he idea of the App is to provide the Cloud credentials I need only when required. Otherwise, the Cloud Credentials file is cleaned and not accessible to any attackers. We integrate the project with specific services like AWS Single Sign-On, the automatic provisioning of the account available to access, and AWS System Manager Session Manager to access EC2 instances directly from the App. I'm also finalizing the Access to other Cloud providers (Google Cloud Platform and Alibaba Cloud) in the following months. Hundreds of developers are downloading it, and the most common reaction is: "It's addictive. I don't want to go back to anything else." After all those requests, from today, we will help the company-wide adoption of the project with enterprise support of the open-source project. https://www.leapp.cloud/support
In Show HN: Leapp – Multi-cloud credentials tool for developers

Showing the 15 most recent of 16 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.