faker_researcher_ids
A Python package extending Faker to generate fake author identifiers used in scientific databases and publication tracking systems:
- Scopus;
- ORCID;
- Web of Science;
- Google Scholar.
Installation
Install with pip:
pip install faker_researcher_ids
Or with uv:
uv add faker_researcher_ids
Usage
- Import necessary dependencies:
from faker import Faker
from faker_researcher_ids import ScientificProvider
- Create a
Fakerinstance:
fake = Faker()
- Add the provider to created instance:
fake.add_provider(ScientificProvider)
Identifiers generation
# Scopus Author ID
>>> fake.scopus_id()
'53070267764'
# Web of Science ID (aka ResearcherID)
>>> fake.wos_id()
'O-2416-2014'
# ORCID
>>> fake.orcid()
'https://orcid.org/0009-0008-7383-0730'
# Google Scholar ID
>>> fake.google_scholar_id()
'ogf35PW74DCe'
Metadata
Release files for faker-researcher-ids 0.1.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 | Provenance | |
|---|---|---|---|---|
| faker_researcher_ids-0.1.0.tar.gz | 2.8 kB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| faker_researcher_ids-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 6.8 kB
Release files / faker_researcher_ids-0.1.0.tar.gz
| Download URL | faker_researcher_ids-0.1.0.tar.gz |
|---|---|
| Size | 2.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
79a220d062f88b9d0afec20b7310638503edac27aeb489653ab4ca59a501d55c
|
|
BLAKE2b-256 checksum How to use checksums |
b85acfc001594573e71d8b74ff564fd078c5b81ac32d23f8fb2b4f1a36812490
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Sep 17, 2025.
Transparency logRelease files / faker_researcher_ids-0.1.0-py3-none-any.whl
| Download URL | faker_researcher_ids-0.1.0-py3-none-any.whl |
|---|---|
| Size | 4.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
7e7adbafe05ed25e63f6655b675a95818fe6b6bef33ca1d656ac925a32fe08cb
|
|
BLAKE2b-256 checksum How to use checksums |
5f42caa9d0b673d58a29ed13318d197cbc6f91de06ddc7f2dbea8faa6f8541ab
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
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 Sep 17, 2025.
Transparency logSecurity for faker-researcher-ids 0.1.0
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.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for faker_researcher_ids-0.1.0.tar.gz
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 Sep 17, 2025.
Transparency logA 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.