
Security News
CISA’s 2025 SBOM Guidance Adds Hashes, Licenses, Tool Metadata, and Context
CISA’s 2025 draft SBOM guidance adds new fields like hashes, licenses, and tool metadata to make software inventories more actionable.
Add this to to your site's Gemfile
:
gem 'jeql'
Add the following to your site's config file (usually _config.yml
):
plugins:
- jeql
After this run bundle install
within your site's directory.
You need to define graphQL endpoints within your Jekyll config. Within the key
jeql
list all your providers in the format:
jeql:
provider_name:
url: "API_ENDPOINT_URL"
header:
Authorization: "HTTP AUTHORIZATION HEADER - SECRET"
An example config to access the graphQL - API from GitHub would look like this:
jeql:
github:
url: "https://api.github.com/graphql"
header:
Authorization: "bearer my-secret-header"
Attention: Make sure to not commit authorization tokens in a public repository. Instead make use of Jekyll's multiple-config-file feature and add these tokens to a private config file which is not checked into your version control system.
Queries in jeql
are specified as json files and live within the _graphql
directory
of your Jekyll site.
An example query file would have the following content:
{
"query": "query { viewer { name repositories(last: 3){ nodes { name }} }}"
}
and would e.g. be stored as /_graphql/last_touched_repositories.json
.
After all this setup has been done you can now use the graphql
block tag in your
template files.
The graphql
tag expects two parameters:
endpoint
is the name of the graphQL - API endpoint as you have it defined in your
Jekyll config file. query
is the name of the file under _graphql
in which you stored
the graphQL query that should be executed against the endpoint (without the .json extension).
An example which uses the settings and query from the paragraphs above would look like this:
{% graphql endpoint: "github", query: "last_touched_repositories" %}
...
{% endgraphql %}
Between the opening and closing graphql
tag you have access to the variable data
which will contain the response of the graphQL query:
<ul>
{% graphql endpoint: "github", query: "last_touched_repositories" %}
{% for repo in data["viewer"]["repositories"]["nodes"] %}
<li>{{repo["name"]}}</li>
{% endfor %}
{% endgraphql %}
</ul>
After checking out the repo, run bin/setup
to install dependencies. Then, run rake spec
to run the tests. You can also run bin/console
for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run bundle exec rake install
. To release a new version, update the version number in version.rb
, and then run bundle exec rake release
, which will create a git tag for the version, push git commits and tags, and push the .gem
file to rubygems.org.
Bug reports and pull requests are welcome on GitHub at https://github.com/Crunch09/jeql. This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the Contributor Covenant code of conduct.
The gem is available as open source under the terms of the MIT License.
Everyone interacting in the jeql project’s codebases, issue trackers, chat rooms and mailing lists is expected to follow the code of conduct.
This gem was inspired by github-metadata and jekyll-seo-tag.
FAQs
Unknown package
We found that jeql demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 1 open source maintainer 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
CISA’s 2025 draft SBOM guidance adds new fields like hashes, licenses, and tool metadata to make software inventories more actionable.
Security News
A clarification on our recent research investigating 60 malicious Ruby gems.
Security News
ESLint now supports parallel linting with a new --concurrency flag, delivering major speed gains and closing a 10-year-old feature request.