'THIS REPOSITORY IS DEPRECATED. ALL OF ITS CONTENT AND HISTORY HAS BEEN MOVED TO GOOGLE-CLOUD-NODE' [//]: # "This README.md file is auto-generated, all changes to this file will be lost." [//]: # "To regenerate it, use python -m synthtool."

Phishing Protection: Node.js Client

Phishing Protection API client for Node.js

A comprehensive list of changes in each version may be found in the CHANGELOG.

• Phishing Protection Node.js Client API Reference
• Phishing Protection Documentation
• github.com/googleapis/nodejs-phishing-protection

Read more about the client libraries for Cloud APIs, including the older Google APIs Client Libraries, in Client Libraries Explained.

Table of contents:

• Quickstart
  • Before you begin
  • Installing the client library
  • Using the client library
• Samples
• Versioning
• Contributing
• License

Quickstart

Before you begin

1. Select or create a Cloud Platform project.
2. Enable billing for your project.
3. Enable the Phishing Protection API.
4. Set up authentication with a service account so you can access the API from your local workstation.

Installing the client library

npm install @google-cloud/phishing-protection

Using the client library

const {
  PhishingProtectionServiceV1Beta1Client,
} = require('@google-cloud/phishing-protection');
const client = new PhishingProtectionServiceV1Beta1Client();

// the numeric project ID.
const formattedParent = client.projectPath(projectId);
const request = {
  parent: formattedParent,
  uri: uri, // the URI to report to Phishing API.
};

await client.reportPhishing(request);

console.info(`reported ${uri} to Phishing Protection API`);

Samples

Samples are in the samples/ directory. Each sample's README.md has instructions for running its sample.

Sample	Source Code	Try it
Quickstart	source code

The Phishing Protection Node.js Client API Reference documentation also contains samples.

Supported Node.js Versions

Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js. If you are using an end-of-life version of Node.js, we recommend that you update as soon as possible to an actively supported LTS version.

Google's client libraries support legacy versions of Node.js runtimes on a best-efforts basis with the following warnings:

• Legacy versions are not tested in continuous integration.
• Some security patches and features cannot be backported.
• Dependencies cannot be kept up-to-date.

Client libraries targeting some end-of-life versions of Node.js are available, and can be installed through npm dist-tags. The dist-tags follow the naming convention legacy-(version). For example, npm install @google-cloud/phishing-protection@legacy-8 installs client libraries for versions compatible with Node.js 8.

Versioning

This library follows Semantic Versioning.

This library is considered to be in preview. This means it is still a work-in-progress and under active development. Any release is subject to backwards-incompatible changes at any time.

More Information: Google Cloud Platform Launch Stages

Contributing

Contributions welcome! See the Contributing Guide.

Please note that this README.md, the samples/README.md, and a variety of configuration files in this repository (including .nycrc and tsconfig.json) are generated from a central template. To edit one of these files, make an edit to its templates in directory.

License

Apache Version 2.0

See LICENSE