Analyzed
6 months
ago.
Project Summary
The premise is this: you're writing or reading about (insert web 2.0 service here)'s new developer API, and you want to either test it, or quickly consume it without waiting for someone to write an official client for it. Huzzah! Bricklayer to the rescue. In just a few lines, you can be pulling the info you need.
http://heypanda.com/posts/48-Writing-a-Ruby-Client-for-a-RESTful-Web-Service-using-Bricklayer
In a Nutshell, Bricklayer...
BSD 3-clause "New" or "Revised" License
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.
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
Did You Know...
-
...
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
-
...
there are over 3,000 projects on the Open Hub with security vulnerabilities reported against them
-
...
anyone with an Open Hub account can update a project's tags
