Download the PHP package snipe/safebrowsing without Composer
On this page you can find all versions of the php package snipe/safebrowsing. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download snipe/safebrowsing
More information about snipe/safebrowsing
Files in snipe/safebrowsing
Package safebrowsing
Short Description Laravel package to allow you to easily integrate the Google Safebrowing API into your application.
License GPL
Homepage https://github.com/Snipe/Safebrowsing
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package safebrowsing
Safebrowsing
This is a Laravel 5 package to enable you to easily interface with the Google Safebrowsing API. (Other RBL services are coming.)
Right now it's only using the Google Safebrowsing Lookup API (v4), but I'll be updating it to include the Update API as well. The old Safebrowsing v3 (non-package) version of this script has also included Phishtank and several RBLs, but I think the RBLs have changed how they work so that old code doesn't work anymore.
This package requires that you have an active Google Safebrowsing API key. It absolutely will not work without one. It's free to create an API key (although the process is every bit as confusing and convoluted as you would expect from Google).
Bear in mind that Google does throttle API usage, so if you have a high-traffic site, you may want to build in a caching layer or something so you don't burn through your requests too quickly. You can keep an eye on your usage through the Google API console.
This package is very rough around the edges and probably shouldn't be used for production yet.
Install
Via Composer
Update Your Config
For applications using Laravel =< 5.4
Open config/app.php and add:
to your providers array in config/app.php, and:
to your aliases array in config/app.php.
Publish the config
Set Your Google Safebrowsing API Key
In your .env, add:
There are additional options in the config file that relate to what specific types of threats you want to check for, and what platforms you want to check on, but you only really need to worry about that if you want to check fewer things, as it's pretty inclusive already.
Usage
Using Blade Syntax
or
where $url is an array of URLs that you would like to check against the Google Safebrowsing API.
Using Facades
Test URLs
Here are some handy test urls you can use while you're experimenting with the system.
- http://www.yahoo.com/ (OK)
- http://www.google.com/ (OK)
- http://malware.testing.google.test/testing/malware/ (Malware)
- http://twitter.com/ (OK)
- http://ianfette.org (malware)
- https://github.com/ (OK)
Change log
Please see CHANGELOG for more information what has changed recently.
Testing
From the package
Contributing
Please see CONDUCT for details.
Security
If you discover any security related issues, please email [email protected] instead of using the issue tracker.
Credits
- A. Gianotto
- All Contributors
License
GNU GENERAL PUBLIC LICENSE. Please see License File for more information.
