Ceridwen Library Self Issue Client

I Use This!

Activity Not Available

Analyzed 12 months ago. based on code collected over 4 years ago.

Project Summary

The Ceridwen Self Issue Client software can provide library users with the ability to check out books to themselves rather than relying on a staffed circulation desk. It presents a graphical interface to the library user and communicates with the back-end library system via a network.

The Ceridwen Self Issue Client software is Java based and supports any library system running the 3M SIP protocol (SIP2). It can also work with barcode readers and JavaCard compatible RFID readers. Whilst it can be made to work with security systems, it has a special Trust mode for libraries without a security system who just wish to allow their patrons to record when they have taken a book. It can also be configured to automatically run in an offline backup mode when the library system is unavailable.

In a Nutshell, Ceridwen Library Self Issue Client...

...
has had 637 commits made by 1 contributors
representing 17,039 lines of code
...
is mostly written in Java
with an average number of source code comments
...
has a well established, mature codebase
maintained by one developer
with increasing Y-O-Y commits
...
took an estimated 4 years of effort (COCOMO model)
starting with its first commit in October, 2004
ending with its most recent commit about 1 year ago

Quick Reference

(2 Locations)

Licenses

GNU General Public License v3.0 or later

Permitted

Commercial Use

Modify

Distribute

Place Warranty

Use Patent Claims

Forbidden

Sub-License

Hold Liable

Required

Distribute Original

Disclose Source

Include Copyright

State Changes

Include License

Include Install Instructions

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

All Licenses

Project Security

Vulnerabilities per Version ( last 10 releases )

There are no reported vulnerabilities

Project Vulnerability Report

Security Confidence Index

Poor security track-record

Favorable security track-record

Vulnerability Exposure Index

Many reported vulnerabilities

Few reported vulnerabilities

About Project Vulnerability Report

Did You Know...

...
in 2016, 47% of companies did not have formal process in place to track OS code
...
by exploring contributors within projects, you can view details on every commit they have made to that project
...
65% of companies leverage OSS to speed application development in 2016
...
anyone with an Open Hub account can update a project's tags

About Project Security