BlueSkySight
A client to gather vulnerability-related information from Bluesky. The collected data is then sent to the Vulnerability-Lookup API as sightings.
Installation
pipx is an easy way to install and run Python applications in isolated environments. It's easy to install.
$ pipx install BlueSkySight
$ export BLUESKYSIGHT_CONFIG=~/.BlueSkySight/conf.py
The configuration should be defined in a Python file (e.g., ~/.BlueSkySight/conf.py).
You must then set an environment variable (BLUESKYSIGHT_CONFIG) with the full path to this file.
You can have a look at this example of configuration.
With Docker
git clone https://github.com/vulnerability-lookup/BlueSkySight
cd BlueSkySight
# Make sure conf.py exists in the project root before running
docker compose up --build
[!NOTE] The docker-compose.yml expects a conf.py file in the root directory. You can create it manually or copy the provided example:
$ cp blueskysight/conf_sample.py conf.py
Streaming the Firehose
BlueSkySight-Firehose streams data from the Bluesky's firehose and uses PyVulnerabilityLookup to create sightings in Vulnerability-Lookup.
$ BlueSkySight-Firehose
Connecting to the Bluesky firehose…
Connection established.
Streaming a Jetstream service
BlueSkySight-Jetstream connects to Bluesky's firehose via Jetstream.
$ BlueSkySight-Jetstream --help
usage: BlueSkySight-Jetstream [-h] [--collections COLLECTIONS] [--geo {us-east,us-west}] [--instance {1,2}]
Connect to a Jetstream service.
options:
-h, --help show this help message and exit
--collections COLLECTIONS
The collections to subscribe to. If not provided, subscribe to all.
--geo {us-east,us-west}
Region of the Jetstream service.
--instance {1,2} Instance of the Jetstream service.
$ BlueSkySight-Jetstream
Connecting to the Bluesky Jetstream at wss://jetstream1.us-west.bsky.network/subscribe?wantedCollections=app.bsky.feed.post…
Connection established. Listening for messages…
License
BlueSkySight is licensed under GNU General Public License version 3
Copyright (c) 2024-2026 Computer Incident Response Center Luxembourg (CIRCL)
Copyright (C) 2024-2026 Cédric Bonhomme - https://github.com/cedricbonhomme
Release files for BlueSkySight 1.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| blueskysight-1.2.0.tar.gz | 26.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| blueskysight-1.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 55.5 kB
Release files / blueskysight-1.2.0.tar.gz
| Download URL | blueskysight-1.2.0.tar.gz |
|---|---|
| Size | 26.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f550f6fcd8420af65a5937fc8dbf1567b5fb1c3202d408009083205e3852bdbe
|
|
BLAKE2b-256 checksum How to use checksums |
db9e3160b220c6d662b0603f90da39c9f0bc517a50550f9bbca0d68d349e7d60
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 29, 2026.
Transparency logRelease files / blueskysight-1.2.0-py3-none-any.whl
| Download URL | blueskysight-1.2.0-py3-none-any.whl |
|---|---|
| Size | 29.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
51af8ab8a1fb8cb5547cf1ab93c8a88a8616dab51d8956531aa2a91c5d71bf44
|
|
BLAKE2b-256 checksum How to use checksums |
17bb5a6754df118fe5d9c916e27fb26274f3132c1099e53f3390afb74a116742
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 29, 2026.
Transparency log