Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
Socket
Sign inDemoInstall
Socket
Sign inDemoInstall

@types/newrelic

Package Overview
Dependencies
Maintainers
1
Versions
28
Alerts
File Explorer

Advanced tools

License
Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@types/newrelic - npm Package Compare versions

Comparing version 3.3.0 to 3.3.1

629

newrelic/index.d.ts

@@ -7,346 +7,341 @@ // Type definitions for newrelic 3.3

// https://docs.newrelic.com/docs/agents/nodejs-agent/api-guides/nodejs-agent-api
declare namespace newrelic {
interface NewRelicAPI {
/**
* Give the current transaction a custom name.
*
* Overrides any New Relic naming rules set in configuration or from New Relic's servers.
*
* IMPORTANT: this function must be called when a transaction is active. New
* Relic transactions are tied to web requests, so this method may be called
* from within HTTP or HTTPS listener functions, Express routes, or other
* contexts where a web request or response object are in scope.
*
* The `name` will be prefixed with 'Custom/' when sent.
*/
setTransactionName(name: string): void;
/**
* Returns a handle on the currently executing transaction.
*
* This handle can then be used to end or ignore a given transaction safely from any context.
* It is best used with newrelic.startWebTransaction() and newrelic.startBackgroundTransaction().
*/
getTransaction(): TransactionHandle;
/**
* Give the current transaction a custom name.
*
* Overrides any New Relic naming rules set in configuration or from New Relic's servers.
*
* IMPORTANT: this function must be called when a transaction is active. New
* Relic transactions are tied to web requests, so this method may be called
* from within HTTP or HTTPS listener functions, Express routes, or other
* contexts where a web request or response object are in scope.
*
* The `name` will be prefixed with 'Custom/' when sent.
*/
export function setTransactionName(name: string): void;
/**
* Specify the `Dispatcher` and `Dispatcher Version` environment values.
*
* A dispatcher is typically the service responsible for brokering
* the request with the process responsible for responding to the
* request. For example Node's `http` module would be the dispatcher
* for incoming HTTP requests.
*/
setDispatcher(name: string, version?: string): void;
/**
* Returns a handle on the currently executing transaction.
*
* This handle can then be used to end or ignore a given transaction safely from any context.
* It is best used with newrelic.startWebTransaction() and newrelic.startBackgroundTransaction().
*/
export function getTransaction(): TransactionHandle;
/**
* Give the current transaction a name based on your own idea of what
* constitutes a controller in your Node application. Also allows you to
* optionally specify the action being invoked on the controller. If the action
* is omitted, then the API will default to using the HTTP method used in the
* request (e.g. GET, POST, DELETE). Overrides any New Relic naming rules set
* in configuration or from New Relic's servers.
*
* IMPORTANT: this function must be called when a transaction is active. New
* Relic transactions are tied to web requests, so this method may be called
* from within HTTP or HTTPS listener functions, Express routes, or other
* contexts where a web request or response object are in scope.
*
* The `name` will be prefixed with 'Controller/' when sent.
* The `action` defaults to the HTTP method used for the request.
*/
setControllerName(name: string, action: string): void;
/**
* Specify the `Dispatcher` and `Dispatcher Version` environment values.
*
* A dispatcher is typically the service responsible for brokering
* the request with the process responsible for responding to the
* request. For example Node's `http` module would be the dispatcher
* for incoming HTTP requests.
*/
export function setDispatcher(name: string, version?: string): void;
/**
* Add a custom attribute to the current transaction.
*
* Some attributes are reserved (see CUSTOM_BLACKLIST in the docs for the current, very short list), and
* as with most API methods, this must be called in the context of an
* active transaction.
*
* Most recently set value wins.
*/
addCustomAttribute(key: string, value: string): void;
/**
* Give the current transaction a name based on your own idea of what
* constitutes a controller in your Node application. Also allows you to
* optionally specify the action being invoked on the controller. If the action
* is omitted, then the API will default to using the HTTP method used in the
* request (e.g. GET, POST, DELETE). Overrides any New Relic naming rules set
* in configuration or from New Relic's servers.
*
* IMPORTANT: this function must be called when a transaction is active. New
* Relic transactions are tied to web requests, so this method may be called
* from within HTTP or HTTPS listener functions, Express routes, or other
* contexts where a web request or response object are in scope.
*
* The `name` will be prefixed with 'Controller/' when sent.
* The `action` defaults to the HTTP method used for the request.
*/
export function setControllerName(name: string, action: string): void;
/**
* Adds all custom attributes in an object to the current transaction.
*
* See documentation for `addCustomAttribute` for more information on setting custom attributes.
*/
addCustomAttributes(atts: { [key: string]: string }): void;
/**
* Add a custom attribute to the current transaction.
*
* Some attributes are reserved (see CUSTOM_BLACKLIST in the docs for the current, very short list), and
* as with most API methods, this must be called in the context of an
* active transaction.
*
* Most recently set value wins.
*/
export function addCustomAttribute(key: string, value: string): void;
/**
* Tell the tracer whether to ignore the current transaction.
*
* The most common use for this will be to mark a transaction as ignored (maybe it's handling
* a websocket polling channel, or maybe it's an external call you don't care
* is slow), but it's also useful when you want a transaction that would
* otherwise be ignored due to URL or transaction name normalization rules
* to *not* be ignored.
*/
setIgnoreTransaction(ignored: boolean): void;
/**
* Adds all custom attributes in an object to the current transaction.
*
* See documentation for `addCustomAttribute` for more information on setting custom attributes.
*/
export function addCustomAttributes(atts: { [key: string]: string }): void;
/**
* Send errors to New Relic that you've already handled yourself.
*
* NOTE: Errors that are recorded using this method do _not_ obey the `ignore_status_codes` configuration.
*
* Optional. Any custom attributes to be displayed in the New Relic UI.
*/
noticeError(error: Error, customAttributes?: { [key: string]: string }): void;
/**
* Tell the tracer whether to ignore the current transaction.
*
* The most common use for this will be to mark a transaction as ignored (maybe it's handling
* a websocket polling channel, or maybe it's an external call you don't care
* is slow), but it's also useful when you want a transaction that would
* otherwise be ignored due to URL or transaction name normalization rules
* to *not* be ignored.
*/
export function setIgnoreTransaction(ignored: boolean): void;
/**
* If the URL for a transaction matches the provided pattern, name the
* transaction with the provided name.
*
* If there are capture groups in the pattern (which is a standard JavaScript regular expression,
* and can be passed as either a RegExp or a string), then the substring matches ($1, $2,
* etc.) are replaced in the name string. BE CAREFUL WHEN USING SUBSTITUTION.
* If the replacement substrings are highly variable (i.e. are identifiers,
* GUIDs, or timestamps), the rule will generate too many metrics and
* potentially get your application blacklisted by New Relic.
*
* An example of a good rule with replacements:
*
* newrelic.addNamingRule('^/storefront/(v[1-5])/(item|category|tag)', 'CommerceAPI/$1/$2')
*
* An example of a bad rule with replacements:
*
* newrelic.addNamingRule('^/item/([0-9a-f]+)', 'Item/$1')
*
* Keep in mind that the original URL and any query parameters will be sent
* along with the request, so slow transactions will still be identifiable.
*
* Naming rules can not be removed once added. They can also be added via the
* agent's configuration. See configuration documentation for details.
*/
addNamingRule(pattern: RegExp | string, name: string): void;
/**
* Send errors to New Relic that you've already handled yourself.
*
* NOTE: Errors that are recorded using this method do _not_ obey the `ignore_status_codes` configuration.
*
* Optional. Any custom attributes to be displayed in the New Relic UI.
*/
export function noticeError(error: Error, customAttributes?: { [key: string]: string }): void;
/**
* If the URL for a transaction matches the provided pattern, ignore the transaction attached to that URL.
*
* Useful for filtering socket.io connections and other long-polling requests out of your agents to keep
* them from distorting an app's apdex or mean response time.
*
* Example:
*
* newrelic.addIgnoringRule('^/socket\\.io/')
*/
addIgnoringRule(pattern: RegExp | string): void;
/**
* If the URL for a transaction matches the provided pattern, name the
* transaction with the provided name.
*
* If there are capture groups in the pattern (which is a standard JavaScript regular expression,
* and can be passed as either a RegExp or a string), then the substring matches ($1, $2,
* etc.) are replaced in the name string. BE CAREFUL WHEN USING SUBSTITUTION.
* If the replacement substrings are highly variable (i.e. are identifiers,
* GUIDs, or timestamps), the rule will generate too many metrics and
* potentially get your application blacklisted by New Relic.
*
* An example of a good rule with replacements:
*
* newrelic.addNamingRule('^/storefront/(v[1-5])/(item|category|tag)', 'CommerceAPI/$1/$2')
*
* An example of a bad rule with replacements:
*
* newrelic.addNamingRule('^/item/([0-9a-f]+)', 'Item/$1')
*
* Keep in mind that the original URL and any query parameters will be sent
* along with the request, so slow transactions will still be identifiable.
*
* Naming rules can not be removed once added. They can also be added via the
* agent's configuration. See configuration documentation for details.
*/
export function addNamingRule(pattern: RegExp | string, name: string): void;
/**
* Get the <script>...</script> header necessary for Browser Monitoring.
*
* This script must be manually injected into your templates, as high as possible
* in the header, but _after_ any X-UA-COMPATIBLE HTTP-EQUIV meta tags.
* Otherwise you may hurt IE!
*
* This method must be called _during_ a transaction, and must be called every
* time you want to generate the headers.
*
* Do *not* reuse the headers between users, or even between requests.
*/
getBrowserTimingHeader(): string;
/**
* If the URL for a transaction matches the provided pattern, ignore the transaction attached to that URL.
*
* Useful for filtering socket.io connections and other long-polling requests out of your agents to keep
* them from distorting an app's apdex or mean response time.
*
* Example:
*
* newrelic.addIgnoringRule('^/socket\\.io/')
*/
export function addIgnoringRule(pattern: RegExp | string): void;
/**
* Instrument a particular method to improve visibility into a transaction,
* or optionally turn it into a metric.
*
* The name defines a name for the segment. This name will be visible in transaction traces and
* as a new metric in the New Relic UI.
* The record flag defines whether the segment should be recorded as a metric.
* The handler is the function you want to track as a segment.
* The optional callback is a function passed to the handler to fire after its work is done.
*
* The agent begins timing the segment when startSegment is called.
* The segment is ended when either the handler finishes executing, or callback is fired, if it is provided.
* If a promise is returned from the handler, the segment's ending will be tied to that promise resolving or rejecting.
*/
startSegment<T extends PromiseLike<any>>(name: string, record: boolean, handler: T): T;
startSegment<T, C extends (...args: any[]) => any>(name: string, record: boolean, handler: (cb?: C) => T, callback?: C): T;
/**
* Get the <script>...</script> header necessary for Browser Monitoring.
*
* This script must be manually injected into your templates, as high as possible
* in the header, but _after_ any X-UA-COMPATIBLE HTTP-EQUIV meta tags.
* Otherwise you may hurt IE!
*
* This method must be called _during_ a transaction, and must be called every
* time you want to generate the headers.
*
* Do *not* reuse the headers between users, or even between requests.
*/
export function getBrowserTimingHeader(): string;
/**
* Instrument a particular callback to improve visibility into a transaction.
*
* Use this API call to improve instrumentation of a particular method, or to track work across asynchronous
* boundaries by calling createTracer() in both the target function and its parent asynchronous function.
*
* The name will be visible in transaction traces and as a new metric in the New Relic UI.
*
* The agent begins timing the segment when createTracer is called, and ends the segment when the callback
* defined by the callback argument finishes executing.
*
* @deprecated
* This method has been deprecated in favor of newrelic.startSegment()
*/
createTracer<T extends (...args: any[]) => any>(name: string, handle: T): T;
/**
* Instrument a particular method to improve visibility into a transaction,
* or optionally turn it into a metric.
*
* The name defines a name for the segment. This name will be visible in transaction traces and
* as a new metric in the New Relic UI.
* The record flag defines whether the segment should be recorded as a metric.
* The handler is the function you want to track as a segment.
* The optional callback is a function passed to the handler to fire after its work is done.
*
* The agent begins timing the segment when startSegment is called.
* The segment is ended when either the handler finishes executing, or callback is fired, if it is provided.
* If a promise is returned from the handler, the segment's ending will be tied to that promise resolving or rejecting.
*/
export function startSegment<T extends PromiseLike<any>>(name: string, record: boolean, handler: T): T;
export function startSegment<T, C extends (...args: any[]) => any>(name: string, record: boolean, handler: (cb?: C) => T, callback?: C): T;
/**
* Creates and starts a web transaction to record work done in the handle supplied.
*
* This transaction will run until the handle
* synchronously returns UNLESS:
* 1. The handle function returns a promise, where the end of the
* transaction will be tied to the end of the promise returned.
* 2. `getTransaction` is called in the handle, flagging the
* transaction as externally handled. In this case the transaction
* will be ended when `TransactionHandle#end` is called in the user's code.
*
* @example
* var newrelic = require('newrelic')
* newrelic.startWebTransaction('/some/url/path', function() {
* var transaction = newrelic.getTransaction()
* setTimeout(function() {
* // do some work
* transaction.end()
* }, 100)
* })
*
* The `url` is used to name and group related transactions in APM,
* so it should be a generic name and not include any variable parameters.
*/
startWebTransaction(url: string, handle: (...args: any[]) => any): any;
/**
* Instrument a particular callback to improve visibility into a transaction.
*
* Use this API call to improve instrumentation of a particular method, or to track work across asynchronous
* boundaries by calling createTracer() in both the target function and its parent asynchronous function.
*
* The name will be visible in transaction traces and as a new metric in the New Relic UI.
*
* The agent begins timing the segment when createTracer is called, and ends the segment when the callback
* defined by the callback argument finishes executing.
*
* @deprecated
* This method has been deprecated in favor of newrelic.startSegment()
*/
export function createTracer<T extends (...args: any[]) => any>(name: string, handle: T): T;
/**
* Creates and starts a background transaction to record work done in the handle supplied.
*
* This transaction will run until the handle
* synchronously returns UNLESS:
* 1. The handle function returns a promise, where the end of the
* transaction will be tied to the end of the promise returned.
* 2. `API#getTransaction` is called in the handle, flagging the
* transaction as externally handled. In this case the transaction
* will be ended when `TransactionHandle#end` is called in the user's code.
*
* @example
* var newrelic = require('newrelic')
* newrelic.startBackgroundTransaction('Red October', 'Subs', function() {
* var transaction = newrelic.getTransaction()
* setTimeout(function() {
* // do some work
* transaction.end()
* }, 100)
* })
*
* The `url` is used to name and group related transactions in APM,
* so it should be a generic name and not include any variable parameters.
*
* The optional `group can be used for grouping background transactions in APM.
* For more information see:
* https://docs.newrelic.com/docs/apm/applications-menu/monitoring/transactions-page#txn-type-dropdown
*/
startBackgroundTransaction(name: string, handle: (...args: any[]) => any): any;
startBackgroundTransaction(name: string, group: string, handle: (...args: any[]) => any): any;
/**
* Creates and starts a web transaction to record work done in the handle supplied.
*
* This transaction will run until the handle
* synchronously returns UNLESS:
* 1. The handle function returns a promise, where the end of the
* transaction will be tied to the end of the promise returned.
* 2. `getTransaction` is called in the handle, flagging the
* transaction as externally handled. In this case the transaction
* will be ended when `TransactionHandle#end` is called in the user's code.
*
* @example
* var newrelic = require('newrelic')
* newrelic.startWebTransaction('/some/url/path', function() {
* var transaction = newrelic.getTransaction()
* setTimeout(function() {
* // do some work
* transaction.end()
* }, 100)
* })
*
* The `url` is used to name and group related transactions in APM,
* so it should be a generic name and not include any variable parameters.
*/
export function startWebTransaction(url: string, handle: (...args: any[]) => any): any;
/**
* End the current web or background custom transaction.
*
* This method requires being in the correct transaction context when called.
*/
endTransaction(): void;
/**
* Creates and starts a background transaction to record work done in the handle supplied.
*
* This transaction will run until the handle
* synchronously returns UNLESS:
* 1. The handle function returns a promise, where the end of the
* transaction will be tied to the end of the promise returned.
* 2. `API#getTransaction` is called in the handle, flagging the
* transaction as externally handled. In this case the transaction
* will be ended when `TransactionHandle#end` is called in the user's code.
*
* @example
* var newrelic = require('newrelic')
* newrelic.startBackgroundTransaction('Red October', 'Subs', function() {
* var transaction = newrelic.getTransaction()
* setTimeout(function() {
* // do some work
* transaction.end()
* }, 100)
* })
*
* The `url` is used to name and group related transactions in APM,
* so it should be a generic name and not include any variable parameters.
*
* The optional `group can be used for grouping background transactions in APM.
* For more information see:
* https://docs.newrelic.com/docs/apm/applications-menu/monitoring/transactions-page#txn-type-dropdown
*/
export function startBackgroundTransaction(name: string, handle: (...args: any[]) => any): any;
export function startBackgroundTransaction(name: string, group: string, handle: (...args: any[]) => any): any;
/**
* Record an event-based metric, usually associated with a particular duration.
*
* The `name` must be a string following standard metric naming rules. The `value` will
* usually be a number, but it can also be an object.
* * When `value` is a numeric value, it should represent the magnitude of a measurement
* associated with an event; for example, the duration for a particular method call.
* * When `value` is an object, it must contain count, total, min, max, and sumOfSquares
* keys, all with number values. This form is useful to aggregate metrics on your own
* and report them periodically; for example, from a setInterval. These values will
* be aggregated with any previously collected values for the same metric. The names
* of these keys match the names of the keys used by the platform API.
*/
recordMetric(name: string, value: number | Metric): void;
/**
* End the current web or background custom transaction.
*
* This method requires being in the correct transaction context when called.
*/
export function endTransaction(): void;
/**
* Update a metric that acts as a simple counter.
*
* The count of the selected metric will be incremented by the specified amount, defaulting to 1.
*/
incrementMetric(name: string, value?: number): void;
/**
* Record an event-based metric, usually associated with a particular duration.
*
* The `name` must be a string following standard metric naming rules. The `value` will
* usually be a number, but it can also be an object.
* * When `value` is a numeric value, it should represent the magnitude of a measurement
* associated with an event; for example, the duration for a particular method call.
* * When `value` is an object, it must contain count, total, min, max, and sumOfSquares
* keys, all with number values. This form is useful to aggregate metrics on your own
* and report them periodically; for example, from a setInterval. These values will
* be aggregated with any previously collected values for the same metric. The names
* of these keys match the names of the keys used by the platform API.
*/
export function recordMetric(name: string, value: number | Metric): void;
/**
* Record an event-based metric, usually associated with a particular duration.
*
* `eventType` must be an alphanumeric string less than 255 characters.
* The keys of `attributes` must be shorter than 255 characters.
*/
recordCustomEvent(eventType: string, attributes: { [keys: string]: boolean | number | string }): void;
/**
* Update a metric that acts as a simple counter.
*
* The count of the selected metric will be incremented by the specified amount, defaulting to 1.
*/
export function incrementMetric(name: string, value?: number): void;
/**
* Registers an instrumentation function.
*
* The provided onRequire callback will be fired when the given module is loaded with require.
* The moduleName parameter should be the string that will be passed to require;
* for example, 'express' or 'amqplib/callback_api'.
*
* The optional onError callback is called if the onRequire parameters throws an error.
* This is useful for debugging your instrumentation.
*
* Use this method to:
* - Add instrumentation for modules not currently instrumented by New Relic.
* - Instrument your own code.
* - Replace the Node.js agent's built-in instrumentation with your own.
*/
instrument: Instrument;
/**
* Record an event-based metric, usually associated with a particular duration.
*
* `eventType` must be an alphanumeric string less than 255 characters.
* The keys of `attributes` must be shorter than 255 characters.
*/
export function recordCustomEvent(eventType: string, attributes: { [keys: string]: boolean | number | string }): void;
/**
* Sets an instrumentation callback for a datastore module.
*
* This method is just like `instrument`, except it provides a datastore-service-specialized shim.
*/
instrumentDatastore: Instrument;
/**
* Registers an instrumentation function.
*
* The provided onRequire callback will be fired when the given module is loaded with require.
* The moduleName parameter should be the string that will be passed to require;
* for example, 'express' or 'amqplib/callback_api'.
*
* The optional onError callback is called if the onRequire parameters throws an error.
* This is useful for debugging your instrumentation.
*
* Use this method to:
* - Add instrumentation for modules not currently instrumented by New Relic.
* - Instrument your own code.
* - Replace the Node.js agent's built-in instrumentation with your own.
*/
export const instrument: Instrument;
/**
* Sets an instrumentation callback for a web framework module.
*
* This method is just like `instrument`, except it provides a web-framework-specialized shim.
*/
instrumentWebframework: Instrument;
/**
* Sets an instrumentation callback for a datastore module.
*
* This method is just like `instrument`, except it provides a datastore-service-specialized shim.
*/
export const instrumentDatastore: Instrument;
/**
* Sets an instrumentation callback for a message service client module.
*
* This method is just like `instrument`, except it provides a message-service-specialized shim.
*/
instrumentMessages: Instrument;
/**
* Sets an instrumentation callback for a web framework module.
*
* This method is just like `instrument`, except it provides a web-framework-specialized shim.
*/
export const instrumentWebframework: Instrument;
/**
* Gracefully shuts down the agent.
*
* If `collectPendingData` is true, the agent will send any pending data to the collector
* before shutting down. Defaults to `false`.
*/
shutdown(cb?: (error?: Error) => void): void;
shutdown(options?: { collectPendingData?: boolean, timeout?: number }, cb?: (error?: Error) => void): void;
}
/**
* Sets an instrumentation callback for a message service client module.
*
* This method is just like `instrument`, except it provides a message-service-specialized shim.
*/
export const instrumentMessages: Instrument;
interface Instrument {
(opts: { moduleName: string, onRequire: () => void, onError?: (err: Error) => void }): void;
(moduleName: string, onRequire: () => void, onError?: (err: Error) => void): void;
}
/**
* Gracefully shuts down the agent.
*
* If `collectPendingData` is true, the agent will send any pending data to the collector
* before shutting down. Defaults to `false`.
*/
export function shutdown(cb?: (error?: Error) => void): void;
export function shutdown(options?: { collectPendingData?: boolean, timeout?: number }, cb?: (error?: Error) => void): void;
interface Metric {
count: number;
total: number;
min: number;
max: number;
sumOfSquares: number;
}
export interface Instrument {
(opts: { moduleName: string, onRequire: () => void, onError?: (err: Error) => void }): void;
(moduleName: string, onRequire: () => void, onError?: (err: Error) => void): void;
}
interface TransactionHandle {
/**
* End the transaction.
*/
end(callback?: () => any): void;
export interface Metric {
count: number;
total: number;
min: number;
max: number;
sumOfSquares: number;
}
/**
* Mark the transaction to be ignored.
*/
ignore(): void;
}
export interface TransactionHandle {
/**
* End the transaction.
*/
end(callback?: () => any): void;
/**
* Mark the transaction to be ignored.
*/
ignore(): void;
}
declare const api: newrelic.NewRelicAPI;
export = api;

6

newrelic/package.json
{
"name": "@types/newrelic",
"version": "3.3.0",
"version": "3.3.1",
"description": "TypeScript definitions for newrelic",

@@ -16,8 +16,8 @@ "license": "MIT",

"type": "git",
"url": "https://www.github.com/DefinitelyTyped/DefinitelyTyped.git"
"url": "https://github.com/DefinitelyTyped/DefinitelyTyped.git"
},
"scripts": {},
"dependencies": {},
"typesPublisherContentHash": "e7c8133f462161156295cf87ef06eff202c96f1d4e5ca6b3185e0787a346c38c",
"typesPublisherContentHash": "decd8102ee70e986b851529b704d2de86e49d67b92d947c48fffd658da110753",
"typeScriptVersion": "2.0"
}

4

newrelic/README.md

@@ -8,6 +8,6 @@ # Installation

# Details
Files were exported from https://www.github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/newrelic
Files were exported from https://github.com/DefinitelyTyped/DefinitelyTyped/tree/master/types/newrelic
Additional Details
* Last updated: Thu, 29 Mar 2018 22:41:31 GMT
* Last updated: Thu, 11 Oct 2018 22:54:50 GMT
* Dependencies: none

@@ -14,0 +14,0 @@ * Global values: none

SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

About

Packages

npm

Go

Maven

PyPI

Rubygems

Stay in touch

Get open source security insights delivered straight into your inbox.

  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc