5 ms·
Stack Analyser: detect technologies used inside a repo
- jasebell 2y agoDoes anyone remember SpikeSource?
- ramon156 2y agoThis seems cool, and probably aimed at a specific use case. Maybe if you're just starting out on joining a team? My question is if there's something I'm not seeing. How often do people have to do this for it to be a tool? Why couldn't I just check the package.json myself? Or is this aimed at LLM's, so you can run a program instead of letting an LLM guess the tech?
- dangsux 2y ago[dead]
- manvillej 2y agopackage.json does not capture all the technologies in a repository. just the JS ones. This seems to capture full stack technologies. This would be very helpful when evaluating existing projects either as a consultant, new team member, open source, or evaluating a vendor's codebase or project.
- h1fra 2y agoyes it's one of the main use case, discovering and documenting at scale. Even on nodejs project there is more than just the package.json
- ripberge 2y agoI could see this being valuable for sales people
- AznHisoka 2y agoHow so? Most orgs dont have their code public
- bob1029 2y agoCool idea. Have we considered looking at the gitignore and gitattributes files as well? You can often figure out the IDE and other tools someone is using by looking at these.
- h1fra 2y agoindeed never thought of that but could be an interesting data point
- fuzzy2 2y agoAs a counterpoint: I often see technology-specific gitignore files, created from a template, that attempt to cover all commonly used tools. Can't really tell what is actually used from that.
- JoBrad 2y agoIn my experience .gitignore files are often overloaded, so would provide false positives.
- dartos 2y agoYeah I always just put whatever in my .gitignore and never clean it up