Download the PHP package gdata/vaas without Composer

On this page you can find all versions of the php package gdata/vaas. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

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 PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • 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.
Please rate this library. Is it a good library?

Informations about the package vaas

vaas-dotnet-ci vaas-rust-civaas-typescript-ci vaas-ruby-ci vaas-java-ci vaas-python-ci vaas-php-ci vaas-golang-ci

Verdict-as-a-Service

Verdict-as-a-Service (VaaS) is a cloud service that provides capabilities to scan files for malware and other threats. It allows you to easily integrate malware detection in your application with a few lines of code. You can use VaaS to secure any scenario where a file is exchanged or stored, such as:

With minimal effort, you can check a file, URL or hashsum for malicious content. No local installation of any anti-malware product is necessary. VaaS works out of the box, by providing detections from the G DATA cloud. Hosting VaaS on your own Kubernetes cluster, is an option as well.

Simple example in Rust. Check below for more programming languages.

How to get started with VaaS

If you are interested in trying out VaaS, you can sign up on our website to create a free trial account. Visit our registration page and follow the instructions to get started. If you have a business case or specific requirements, please contact us at [email protected] to discuss your needs and explore how VaaS can best fit your organization.

SDKs

We provide SDKs for various programming languages to make it easy for you to integrate VaaS in your application. You can find the source code, examples, and documentation for each SDK in the corresponding repository. Currently, we support the following languages:

Language Source Code Examples Documentation Repository
Rust Rust SDK Examples docs.rs crates.io
Java Java SDK Examples Readme maven central
PHP PHP SDK Examples packagist
TypeScript TypeScript SDK Examples Readme npmjs
Python Python SDK Examples Readme pypi
.NET .NET SDK Examples nuget.org
Ruby Ruby SDK Examples Reamde rubygems
Go Go SDK Examples Readme Github
C++ C++ SDK Readme Github

The following table shows the functionality supported by each SDK:

Functionality Rust Java PHP TypeScript .NET Python Ruby Golang C++
Use HTTP API ❌ ✅ ❌ ❌ ❌ ❌ ❌ ✅ ❌
Check SHA256 ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Check File ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Check URL ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ❌
Check Stream ✅ ✅ ✅ ✅ ✅ ✅ ❌ ✅ ✅

Integration Ideas for Malware Detection trough VaaS

You can use VaaS to create various applications that scan for malicious content with a few lines of code. Here are some examples:

Build & Test

The easiest way to build and test the SDKs is with the Nix Package Manager and the provided Just file. Nix will take care of all dependencies and Just provides a simple interface to run the most common tasks.

To build and test the SDKs, run the following command:

There are test-*, build-*, clean-* and release-* tasks for each SDK, with the exception of Python and PHP, where no build task is available. You can also run the tests for all SDKs with just test-all. A build-all and clean-all task is available as well.

The release-* task triggers a Github Action to build and release a new version of the specified SDK. It needs a version number as an argument, which is used to tag the release. The version number should follow the Semantic Versioning scheme.

As the SDKs need credentials to authenticate to the VaaS API. You need to provide them in a .env file. Copy your .env file into the root directory of the project. The C++ SDK needs special credentials, which you can provide in a .cpp.env file.


# Copy the .env and .cpp.env file to all SDK folders
# to be able to run the integration tests
just populate-env

All versions of vaas with dependencies

PHP Build Version
Package Version
Requires php Version ^8.1
psr/log Version ^1.1 || ^2.0 || ^3.0
amphp/http-client Version ^5.2
amphp/amp Version ^3.0
revolt/event-loop Version ^1.0
amphp/byte-stream Version ^2.1
amphp/socket Version ^2.3
amphp/file Version ^3.2
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package gdata/vaas contains the following files

Loading the files please wait ....