Back office of MONARC
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Ruslan Baidan 05e0ad3d8b Added back the dependency pluging package. 12 hours ago
INSTALL Updated INSTALLATION instructions. 3 months ago
config Migrated to Laminas. 1 day ago
db-bootstrap Updated the core version and cleaned up the initial data script. 2 months ago
deliveries/cases Update templates of deliverables 7 months ago
public Migrated to Laminas. 1 day ago
scripts Simplifying update script. 3 months ago
vagrant updated vagrant bootstrap file 3 months ago
.gitignore Updated .gitignore 3 months ago
AUTHORS Updated README and AUTHORS file. 1 day ago
LICENSE Added license file. 2 years ago
README.md Updated README and AUTHORS file. 1 day ago
VERSION.json Updated README and AUTHORS file. 1 day ago
composer.json Updated the composer.lock with the removed dependency. 1 day ago
composer.lock Added back the dependency pluging package. 12 hours ago
package.json Updated README and AUTHORS file. 1 day ago

README.md

MONARC - Back Office

The back office is especially needed if you want to manage several clients. For more information you can have a look at the differences with MONARC itself or you can check the MONARC architecture.

Documentation

You will find a user guide and a technical guide on the MONARC website.

For installation instructions see INSTALL.

License

This software is licensed under GNU Affero General Public License version 3

For more information, the list of authors and contributors is available.

Data provided with MONARC (threats, assets, vulnerabilities, referentials, etc.) are licensed under CC0 1.0 Universal (CC0 1.0) - Public Domain Dedication. These objects are available through the MONARC Objects Sharing Plarform. If a specific author wants to license an object under a different license, a pull request can be requested.