You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you make a creative work (which includes code), the work is under exclusive copyright by default. Unless you include a license that specifies otherwise, nobody else can copy, distribute, or modify your work without being at risk of take-downs, shake-downs, or litigation. Once the work has other contributors (each a copyright holder), “nobody” starts including you.
I've decided to add an MIT LICENSE file anyways to the repo (crediting Alexis Rondeau, Micha Brugger, and myself) to close this issue and improve this plugin's scorecard on the Obsidian Community Site. It matches the MIT declaration package.json has has always had.
I do have to say that the original author hasn't explicitly signed off on the retroactive grant, so strictly speaking this skirts the legal edges. Package.json always declaring MIT from early on is a decent good-faith signal of the original intent, so practically you should be fine to fork responsibly. If the original author ever surfaces with concerns, I'll inform you.
Activity
Comprehensive-Jason commentedon Feb 3, 2026
I believe the reason why this repo doesn't have a license is that the original, original creator of this plugin ( https://github.com/akaalias/obsidian-footnotes ) didn't give it a license.
ascochran commentedon Feb 7, 2026
@Comprehensive-Jason you're right, we'll need to start over there. I left a comment on an existing issue requesting an explicit license; hopefully we get some traction.
Comprehensive-Jason commentedon Jul 16, 2026
I've decided to add an MIT LICENSE file anyways to the repo (crediting Alexis Rondeau, Micha Brugger, and myself) to close this issue and improve this plugin's scorecard on the Obsidian Community Site. It matches the MIT declaration package.json has has always had.
I do have to say that the original author hasn't explicitly signed off on the retroactive grant, so strictly speaking this skirts the legal edges. Package.json always declaring MIT from early on is a decent good-faith signal of the original intent, so practically you should be fine to fork responsibly. If the original author ever surfaces with concerns, I'll inform you.
ascochran commentedon Jul 16, 2026
Thanks @Comprehensive-Jason !