Security News
Research
Data Theft Repackaged: A Case Study in Malicious Wrapper Packages on npm
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
gatsby-telemetry
Advanced tools
The gatsby-telemetry package is used to collect anonymous usage analytics for Gatsby projects. It helps the Gatsby team understand how developers use Gatsby and improve the framework based on this data.
Enable Telemetry
This feature allows you to enable telemetry tracking for specific CLI commands. The `trackCli` function is used to log the usage of a particular command.
const telemetry = require('gatsby-telemetry');
telemetry.trackCli('CLI_COMMAND_NAME');
Disable Telemetry
This feature allows you to disable telemetry tracking. The `disable` function stops the collection of usage data.
const telemetry = require('gatsby-telemetry');
telemetry.disable();
Track Event
This feature allows you to track custom events. The `track` function logs an event with a specified name and additional data.
const telemetry = require('gatsby-telemetry');
telemetry.track('EVENT_NAME', { key: 'value' });
The analytics-node package is a client for Segment's analytics API. It allows you to track events and user actions in your application. Compared to gatsby-telemetry, analytics-node is more general-purpose and can be used with any application, not just Gatsby.
The amplitude-js package is a JavaScript client for Amplitude's analytics platform. It provides similar functionality to gatsby-telemetry but is designed to work with Amplitude's analytics service, offering more advanced features and integrations.
The mixpanel package is a client for Mixpanel's analytics service. It allows you to track events, user actions, and more. Like gatsby-telemetry, it helps you understand user behavior, but it is part of the broader Mixpanel analytics ecosystem.
Check out gatsby.dev/telemetry for more information.
Capture an event of type type
and decorate the generated event with these tags (note: allowed tags are filtered on server side)
This one does the same thing as the captureEvent
function described above.
Capture an event of type type
and decorate the generated event with these tags (note: allowed tags are filtered on server side)
Capture an error of type type
. The exception maybe passed in tags and it will be sanitized to anonymize the contents.
Capture an build error of type type
. The exception maybe passed in tags and it will be sanitize to anonymize the contents.
Set additional tags to be included in all future events.
Attach additional tags to the next event generated of type type
.
Enable or disable the telemetry collection.
Returns a debounced events tracker for collecting general activity information for incoming requests.
GATSBY_TELEMETRY_DEBUG
to 1
to print the telemetry data instead of sending it overGATSBY_TELEMETRY_DISABLED
to 1
to opt out of all telemetryGATSBY_TELEMETRY_VERBOSE
to 1
to log all telemetryFAQs
Gatsby Telemetry
The npm package gatsby-telemetry receives a total of 203,143 weekly downloads. As such, gatsby-telemetry popularity was classified as popular.
We found that gatsby-telemetry demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 7 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Research
The Socket Research Team breaks down a malicious wrapper package that uses obfuscation to harvest credentials and exfiltrate sensitive data.
Research
Security News
Attackers used a malicious npm package typosquatting a popular ESLint plugin to steal sensitive data, execute commands, and exploit developer systems.
Security News
The Ultralytics' PyPI Package was compromised four times in one weekend through GitHub Actions cache poisoning and failure to rotate previously compromised API tokens.