health-visualizations-front
health-visualizations
| health-visualizations-front | health-visualizations | |
|---|---|---|
| 1 | 1 | |
| 0 | 0 | |
| - | - | |
| 0.0 | 0.0 | |
| 10 months ago | about 1 year ago | |
| JavaScript | Python | |
| MIT License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
health-visualizations-front
-
Tell HN: GitHub will delete your private repo if you lose access to the original
https://github.com/futurice/health-visualizations-front
health-visualizations
-
Tell HN: GitHub will delete your private repo if you lose access to the original
> If the original code was "open source", then why exactly was it in a private repository?
It's been too many years to remember the exact reasons, but this was not the only repo in the project. This was the "working directory" that had all kinds of random stuff that a data science project might accrue over time. Later in the project we published 3 repos which were more "cleaned up" to be potentially useful to outsiders (I use scare quotes around "cleaned up" because the codebases are still a mess, sorry).
Anyway, 3 of the 4 repos appear to still be public:
https://github.com/futurice/health-visualizations
What are some alternatives?
yt-dlp - A feature-rich command-line audio/video downloader
fake-git-history - Generate Git commits.
laaketutka-prereqs - Prerequisites for Laaketutka backend
deno-mirror-to-gitea - Bulk add mirror repositories to a Gitea instance by scraping repositories on GitHub.