| Vulnerabilities | |||||
|---|---|---|---|---|---|
| Version | Suggest | Low | Medium | High | Critical |
0.2026.6.22.1.23.34 - This version is safe to use because it has no known security vulnerabilities at this time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform
Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.
BSD-3-Clause - BSD 3-Clause "New" or "Revised" License.. image:: https://zenodo.org/badge/644894042.svg :target: https://zenodo.org/badge/latestdoi/644894042
Note: This package is not currently meant to be used directly by users, and only meant to be used from the core astropy package.
https://docs.astropy.org/en/latest/utils/iers.html
This project is Copyright (c) Astropy Developers and licensed under
the terms of the BSD 3-Clause license. This package is based upon
the OpenAstronomy packaging guide <https://github.com/OpenAstronomy/packaging-guide>_
which is licensed under the BSD 3-clause licence. See the licenses folder for
more information.
We love contributions! astropy-iers-data is open source, built on open source, and we'd love to have you hang out in our community.
Imposter syndrome disclaimer: We want your help. No, really.
There may be a little voice inside your head that is telling you that you're not ready to be an open source contributor; that your skills aren't nearly good enough to contribute. What could you possibly offer a project like this one?
We assure you - the little voice in your head is wrong. If you can write code at all, you can contribute code to open source. Contributing to open source projects is a fantastic way to advance one's coding skills. Writing perfect code isn't the measure of a good developer (that would disqualify all of us!); it's trying to create something, making mistakes, and learning from those mistakes. That's how we all improve, and we are happy to help others learn.
Being an open source contributor doesn't just mean writing code, either. You can help out by writing documentation, tests, or even giving feedback about the project (and yes - that includes giving feedback about the contribution process). Some of these contributions may be the most valuable to the project as a whole, because you're coming to the project with fresh eyes, so you can see the errors and assumptions that seasoned contributors have glossed over.
Note: This disclaimer was originally written by
Adrienne Lowe <https://github.com/adriennefriend>_ for a
PyCon talk <https://www.youtube.com/watch?v=6Uj746j9Heo>, and was adapted by
astropy-iers-data based on its use in the README file for the
MetPy project <https://github.com/Unidata/MetPy>.
