Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/jgamblin/cveprophet
CVE Prophet
https://github.com/jgamblin/cveprophet
Last synced: 2 months ago
JSON representation
CVE Prophet
- Host: GitHub
- URL: https://github.com/jgamblin/cveprophet
- Owner: jgamblin
- License: mit
- Created: 2021-07-17T19:48:40.000Z (over 3 years ago)
- Default Branch: main
- Last Pushed: 2021-07-18T19:35:24.000Z (over 3 years ago)
- Last Synced: 2024-08-05T17:38:49.672Z (5 months ago)
- Language: Jupyter Notebook
- Size: 4.57 MB
- Stars: 9
- Watchers: 2
- Forks: 3
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
- awesome-hacking-lists - jgamblin/cveprophet - CVE Prophet (Jupyter Notebook)
README
# CVE Prophet
I was recently asked if I had ever thought about trying to predict CVE growth. I had not, or really didn't even know where to start, but after some research, I found the [Prophet project](https://facebook.github.io/prophet/) that is a forecasting algorithm [open-sourced by Facebook](https://research.fb.com/prophet-forecasting-at-scale/) and uses the [GAM family of algorithms](https://en.wikipedia.org/wiki/Generalized_additive_model).
Using prophet with the [NVD data](https://nvd.nist.gov/vuln/data-feeds#JSON_FEED) in a Jupyter notebook was a lot easier than I expected, and for the first iteration, I am thrilled with the outcome.
## Graphs
![Forecast Graph](forecast.jpg)
![ForeCast Changepont Graph](forecast_changepoints.jpg)
## Contributing
Contributions are what make the open source community such an amazing place to be learn, inspire, and create. Any contributions you make are **greatly appreciated**.
1. Fork the Project
2. Create your Feature Branch (`git checkout -b feature/AmazingFeature`)
3. Commit your Changes (`git commit -m 'Add some AmazingFeature'`)
4. Push to the Branch (`git push origin feature/AmazingFeature`)
5. Open a Pull Request## Support
Use the [issues](https://github.com/jgamblin/cveprophet) tab to report any problems or issues.
## License
Distributed under the MIT License. See `LICENSE` for more information.
## Contact
Jerry Gamblin - [@jgamblin](https://twitter.com/jgamblin)