Sylva identity discovery
Note that Sylva is undergoing rapid development and documentation may be quickly obsoleted.
Visit the Sylva Wiki for more information.
Summary
Useful Integrations
| Name | Description | API Key |
|---|---|---|
| Endato | Person data source (phone, address, cell, etc) | Req [ T | $ ] |
| ProxyNova | COMB API (cleartext passwords, usernames) | Native |
| Veriphone | Phone number lookup | Req [ F+ ] |
| GitHub | See detail below | Opt [ F ] |
$ : paid | T : trial | F : Free | F+ : Freemium
Most development was done without any paid access -- so despite some integrations requiring an account, the full experience can be attained without any subscriptions.
GitHub Integration
Query GitHub for any known PGP keys, scrape both the oldest and newest 1000 commit authorships (2000 total) for leaked identifying information, and search for identities based on full name, email, or username.
Personal Access Token (PAT) is required for PGP scraping, but all other functions work out of the box. PAT is recommended for higher rate limits on other functions. PAT does not require any permissions assigned to it whatsoever.
Generic modules
| Name | Description |
|---|---|
| PGP Search | Search for identities through discovered PGP keys |
| Sherlock | Sherlock extended for discovery of additional identities and branching |
| Voter Records | Geographical, relation, and age lookup in 18 US States |
Quick Start
Docker is the preferred method of installation, providing the most consistent and predictable user experience.
docker run --rm -it sylva/sylva --help
Other installation methods are described on the Sylva Wiki.
Packagers
It's recommended that you don't package Sylva yet. Changes are happening at rates quicker than most release cycles allow. If you'd like to package Sylva, feel free to reach out for info!
Contributing
Contributors should refer to our contributing guidelines for information on how to contribute to the project. Note that since the project is still in its infancy, there isn't yet a formal roadmap.
Contributors opening a pull request are assumed to have read and agreed to the guidelines.
Stargazers over time
Metadata
Release files for sylva 0.1.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 |
|---|---|---|---|---|
| sylva-0.1.2.tar.gz | 46.1 kB | Without provenance | Details for sylva-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| sylva-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for sylva-0.1.2-py3-none-any.whl |
Total release size: 101.4 kB
Release files / sylva-0.1.2.tar.gz
| Download URL | sylva-0.1.2.tar.gz |
|---|---|
| Size | 46.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
cb738aa6afd054c4af3ac19175c8625fd3580d3c1a7b80a61080f2006fddcbd1
|
|
BLAKE2b-256 checksum How to use checksums |
d55c41cc0ff2a50b764dd262951216d2e22194fa553ce4e4411629c247251b72
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
pdm/2.17.3 CPython/3.10.12 Linux/6.5.0-1025-azure
|
Release files / sylva-0.1.2-py3-none-any.whl
| Download URL | sylva-0.1.2-py3-none-any.whl |
|---|---|
| Size | 55.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2f21a2061c48b70c973b0a17d41d9844cb6a32f81d52d8b39fa64da95afd1ee5
|
|
BLAKE2b-256 checksum How to use checksums |
235e9d660b399de48ea725abeb3e13c5452ef35900562286dc268c7d84888904
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
pdm/2.17.3 CPython/3.10.12 Linux/6.5.0-1025-azure
|
Security for sylva 0.1.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.