blackwinter-flattendb
Advanced tools
= flattendb - Flatten relational databases
== VERSION
This documentation refers to flattendb version 0.0.4
== DESCRIPTION
TODO: well, the description... ;-)
== LINKS
Documentation:: http://prometheus.rubyforge.org/flattendb Source code (old):: http://prometheus.rubyforge.org/svn/scratch/flattendb Source code:: http://github.com/blackwinter/flattendb Rubyforge project:: http://rubyforge.org/projects/prometheus
== AUTHORS
== LICENSE AND COPYRIGHT
Copyright (C) 2007 University of Cologne, Albertus-Magnus-Platz, 50932 Cologne, Germany
flattendb is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.
flattendb is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.
You should have received a copy of the GNU General Public License along with flattendb. If not, see http://www.gnu.org/licenses/.
FAQs
Unknown package
We found that blackwinter-flattendb demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.
