The list of services makes it look like you’re using endoflife.date as the data source, which I kept under MIT, and requires attribution. We’re happy to support every usecase, but please provide attribution :)
> By default, Metaport uses the API provided by endoflife.date, but alternative backends can be used instead. The following instructions are relevant to Metaport CE in self-managed setups.
If you're building a complete SaaS product on top of an open-source database maintained by volunteers, please credit them better, or support us: https://github.com/sponsors/endoflife-date
The list of services makes it look like you’re using endoflife.date as the data source, which I kept under MIT, and requires attribution. We’re happy to support every usecase, but please provide attribution :)
(Bitcoin-core stands out very much).
Edit: their backend service source does mention endoflife.date as the source, but it is hidden away in the developer docs (https://gitlab.com/dcentrica/metaport/metaport-server/-/blob...)
> By default, Metaport uses the API provided by endoflife.date, but alternative backends can be used instead. The following instructions are relevant to Metaport CE in self-managed setups.
If you're building a complete SaaS product on top of an open-source database maintained by volunteers, please credit them better, or support us: https://github.com/sponsors/endoflife-date
https://endoflife.date/
I’m a fan of your tool. You might want to feature it on NextGen Tools: https://nxgntools.com
Any feedback would be appreciated.