GraphDNA

GraphDNA is a tool that uses multiple heuristics to fingerprint GraphQL endpoints.
Getting Started
It takes only two simple steps to fingerprint an endpoint using GraphDNA.
pip install graphdna
graphdna -u https://example.com/graphql
Options
GraphDNA supports the following options:
graphdna \
# Url to fingerprint
--url/-u https://example.com/graphql \
# Header (chainable)
--header/-H "Authorization: Bearer token"
Supported engines
| Name | Supported | Name | Supported | Name | Supported | ||
|---|---|---|---|---|---|---|---|
| Agoo | ✅ | Apollo | ✅ | Ariadne | ✅ | ||
| AWS AppSync | ✅ | Caliban | ✅ | DGraph | ✅ | ||
| Dianajl | ✅ | Directus | ✅ | Flutter | ✅ | ||
| GQLGen | ✅ | Graphene | ✅ | GraphQLApiForWp | ✅ | ||
| GraphQL-Go | ✅ | gopher/GraphQL-Go | ✅ | GraphQL-Java | ✅ | ||
| GraphQL-PHP | ✅ | GraphQL Yoga | ✅ | Hasura | ✅ | ||
| HyperGraphQL | ✅ | Jaal | ✅ | Juniper | ✅ | ||
| Lacinia | ✅ | Lighthouse | ✅ | Mercurius | ✅ | ||
| MorpheusGraphQL | ✅ | GraphQL Ruby | ✅ | Sangria | ✅ | ||
| Shopify | ✅ | Stepzen | ✅ | Strawberry | ✅ | ||
| Tartiflette | ✅ | WPGraphQL | ✅ |
Environment Variables
Logger - No effect if you pass your own logger
| Name | Values | Default | Behavior |
|---|---|---|---|
LOG_FORMAT |
console, json |
console |
Change the log format accordingly |
DEBUG |
True, False |
False |
Enable debug logging |
Integration
import logging
from typing import Dict, Optional
from graphdna import detect_engine, detect_engine_async
from graphdna.entities import GraphQLEngine
def detect_engine(
url: str,
headers: Optional[Dict[str, str]] = None,
logger: Optional[logging.Logger] = None,
) -> Optional[GraphQLEngine]:
...
async def detect_engine_async(
url: str,
headers: Optional[Dict[str, str]] = None,
logger: Optional[logging.Logger] = None,
) -> Optional[GraphQLEngine]:
...
Local installation
git clone git@github.com:Escape-Technologies/graphdna.git
cd graphdna
chmod +x ./install-dev.sh
./install-dev.sh
Credits
Contributing
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
Please make sure to update tests as appropriate.
License 
Metadata
Release files for graphdna 1.2.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| graphdna-1.2.2.tar.gz | 15.4 kB | Without provenance | Details for graphdna-1.2.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| graphdna-1.2.2-py3-none-any.whl | Python 3 | none | any | Details for graphdna-1.2.2-py3-none-any.whl |
Total release size: 45.9 kB
Release files / graphdna-1.2.2.tar.gz
| Download URL | graphdna-1.2.2.tar.gz |
|---|---|
| Size | 15.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c637ef763bbaef61fcf4f83d6054a1e8a908ee4852955251c0eddb24f718c14a
|
|
BLAKE2b-256 checksum How to use checksums |
9a285b781f6afdf4a01f0962856d6438d3ac3b4c68265af54a99f334c24c59ad
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.3.2 CPython/3.11.0 Linux/5.4.109+
|
Release files / graphdna-1.2.2-py3-none-any.whl
| Download URL | graphdna-1.2.2-py3-none-any.whl |
|---|---|
| Size | 30.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3d491ccbbefa6a411bf2b7ce1bfdcf5f8d72adfe0f6c743ea22fefb783ac435a
|
|
BLAKE2b-256 checksum How to use checksums |
87faef6d076c95ad4191f019d172dbf9dddb3b9c33f8fe51f01b30601d68d88c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
poetry/1.3.2 CPython/3.11.0 Linux/5.4.109+
|
Security for graphdna 1.2.2
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.