kiroku

I Use This!

Inactive

Analyzed about 13 hours ago. based on code collected about 13 hours ago.

Project Summary

Kiroku ('Document' in Japanese) is a CMS system that allows quick creation of websites. As a page-focused system, it allows for a user or multiple users to build a dynamic website with nothing more than HTML knowledge. It supports custom themes using Zend_Layout and is very plug-and-play.

Kiroku separates itself from other CMS solutions such as XOOPS by using modules in a different way - multiple pages can use the same module but the content is separated as opposed to XOOPS or PHPNuke where the module generates a single certain page for you.

For more complicated code, Kiroku leverages the power of the Zend Framework to allow developers to create completely new and dynamic sections to be added to websites. Plugins and Sections are self contained and can easily be shared.

Kiroku was formerly called BiffCMS

In a Nutshell, kiroku...

...
has had 93 commits made by 1 contributors
representing 392,704 lines of code
...
is mostly written in PHP
with a very well-commented source code
...
has a young, but established codebase
maintained by nobody
with stable Y-O-Y commits
...
took an estimated 103 years of effort (COCOMO model)
starting with its first commit in March, 2007
ending with its most recent commit almost 16 years ago

Quick Reference

Project Links:

Homepage

Code Locations:

https://github.com/dragonmantank...

Similar Projects:

Managers:

Chris Tankersley

Licenses

BSD 4-clause (University of California-Specific)

Permitted

Commercial Use

Modify

Distribute

Place Warranty

Forbidden

Hold Liable

Use Trademarks

Required

Include Copyright

Include License

These details are provided for information only. No information here is legal advice and should not be used as such.

All Licenses

This Project has No vulnerabilities Reported Against it

Did You Know...

...
in 2016, 47% of companies did not have formal process in place to track OS code
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
...
by exploring contributors within projects, you can view details on every commit they have made to that project