Security News
New Python Packaging Proposal Aims to Solve Phantom Dependency Problem with SBOMs
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
juttle-gmail-adapter
Advanced tools
Gmail adapter for the Juttle data flow language.
This uses the nodejs API for google to read and write gmail messages. It also uses Batchelor to perform batched email fetches, something that the main google API does not currently support.
read gmail -from :5 days ago: -raw "to:me"
| reduce count() by from
| sort count -desc
| view table -title "Who sends me the most mail?";
read gmail -from :5 days ago: -to :1 day ago: -raw "to:me"
| batch -every :1h:
| reduce count()
| view timechart -title "When during the day do I get mail?"
read gmail -from :5 days ago: -to :1 day ago: -raw "to:me"
| batch -every :1h:
| reduce count()
| write gmail -subject "When during the day do I get mail?"
An end-to-end example is described here and deployed to the demo system demo.juttle.io.
Like Juttle itself, the adapter is installed as a npm package. Both Juttle and the adapter need to be installed side-by-side:
$ npm install juttle
$ npm install juttle-gmail-adapter
The juttle-gmail-adapter fits into the overall Juttle Ecosystem as one of the adapters in the below diagram:
Configuration involves these steps:
.juttle/config.js
To create application credentials, follow the instructions under
Step 1: Turn on the Gmail API on the
nodejs quickstart instructions page. (Steps
2-4 are not necessary--you only need step 1 to create the client api
credentials). This will result in a file on disk titled
client_secret.json
with this structure:
{
"installed": {
"client_id": "--your-client-id--",
"project_id": "--your-project-id",
"auth_uri": "https:\/\/accounts.google.com\/o\/oauth2\/auth",
"token_uri": "https:\/\/accounts.google.com\/o\/oauth2\/token",
"auth_provider_x509_cert_url": "https:\/\/www.googleapis.com\/oauth2\/v1\/certs",
"client_secret": "--your-client-secret-id--",
"redirect_uris": [
"urn:ietf:wg:oauth:2.0:oob",
"http:\/\/localhost"
]
}
}
You'll use this file in the next step.
You need to create an oauth2 token that allows this program to read your email on your behalf.
To do this, run node create_oauth_token.js <path-to-client_secret.json>
. create_oauth_token.js
is in the
top-level directory where juttle-gmail-adapter is installed
(i.e. wherever you ran git clone
for github, under
node_modules/juttle-gmail-adapter
for npm).
This will provide a json config block to add to your .juttle/config.js
file.
This will also use the gmail nodejs api to read the list of labels assocated with the authenticated user, to verify that the token was created successfully.
.juttle/config.js
create_oauth_token.js
printed a configuration block like this:
{
"adapters": {
"gmail": {
"client-credentials": {
"installed": {
"client_id": "--your-client-id--",
"project_id": "--your-project-id",
"auth_uri": "https:\/\/accounts.google.com\/o\/oauth2\/auth",
"token_uri": "https:\/\/accounts.google.com\/o\/oauth2\/token",
"auth_provider_x509_cert_url": "https:\/\/www.googleapis.com\/oauth2\/v1\/certs",
"client_secret": "--your-client-secret-id--",
"redirect_uris": [
"urn:ietf:wg:oauth:2.0:oob",
"http:\/\/localhost"
]
}
},
"oauth2-token": {
"access_token": "---your-access-token---",
"token_type": "Bearer",
"refresh_token": "---your-refresh-token---",
"expiry_date": DDDDDDDDDDDDD
}
}
}
}
Add this configuration to your .juttle/config.js
file. If you
have an existing "adapters" section, for example:
{
"adapters": {
"twitter": {...}
}
}
Add the gmail section as a peer item below "adapters":
{
"adapters": {
"twitter": {...},
"gmail": {...}
}
}
Name | Type | Required | Description |
---|---|---|---|
raw | string | no | Use the following advanced search filter to select messages. |
from | moment | no | select messages after this time (inclusive) |
to | moment | no | select messages before this time (exclusive) |
last | duration | no | shorthand for -from :now: - -to :now: |
lag | duration | no | Controls how long to wait behind real time to fetch datapoints. |
Name | Type | Required | Description |
---|---|---|---|
to | string | no | the to: header of the message. If not specified, defaults to the email address of the authenticated user. |
subject | string | no | the subject of the message. Default is 'Juttle Program Output'. If output is split, " (part )" is appended to subject. |
limit | number | no | split output into batches of points. By default all points are buffered in memory until the program has completed. |
jsonOnly | boolean | no | if true, only include a raw JSON mime part in the email. The default (false) is to attach a plain/text as well as application/json part. |
If you want to write your own adapter, look at the detailed notes on how the Gmail adapter interacts with the Juttle runtime/compiler to fetch messages and pass them as points to the juttle program.
Want to contribute? Awesome! Don’t hesitate to file an issue or open a pull request.
0.6.0
Released 2016-03-23
FAQs
Juttle adapter for Gmail
The npm package juttle-gmail-adapter receives a total of 2 weekly downloads. As such, juttle-gmail-adapter popularity was classified as not popular.
We found that juttle-gmail-adapter demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 3 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
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
Security News
Socket CEO Feross Aboukhadijeh discusses open source security challenges, including zero-day attacks and supply chain risks, on the Cyber Security Council podcast.
Security News
Research
Socket researchers uncover how threat actors weaponize Out-of-Band Application Security Testing (OAST) techniques across the npm, PyPI, and RubyGems ecosystems to exfiltrate sensitive data.