Reggie
A Python package for checking professional registration status across various certification bodies, particularly useful for architecture.
It can check the NSW and QLD ARBs at the moment, but there's potential to add more in the future.
✨✨✨✨✨✨✨✨✨✨✨✨✨✨✨✨✨✨
✨ THIS IS BRAND NEW ✨
✨ ✨
✨There could well be all kinds of issues ✨
✨but if you're here, you're probably ✨
✨the kind of person who can help me find ✨
✨them and fix them! ✨
✨✨✨✨✨✨✨✨✨✨✨✨✨✨✨✨✨✨
Who's it for?
If you're a NSW or QLD architecture practice, then you'll need to keep track of how your people represent themselves on the internet. This can help by checking the registration status of all the registrations that people hold (as long as it's in the list of bodies that this checks, which is only NSW and QLD's ARBs at the moment)
Installation
pip install arch-reggie
Quick Start
from reggie import RegistrationProcessor, ProcessingConfig
# Initialize with default configuration
processor = RegistrationProcessor()
# Process a CSV file - default expects columns: Email, Full Name, LinkedIn URL, State Board Name, Registration Number, State Board Code
results = processor.process_csv("path/to/your/registrations.csv")
# Save results as JSON
processor.save_json(results, "output.json")
CSV Format
The default configuration expects a headerless CSV with these columns in order:
- Full Name
- LinkedIn URL
- State Board Name (e.g., "NSW Architects Registration Board")
- Registration Number
- State Board Code (e.g., "NSW", "QLD")
Supported Registration Bodies
- NSW Architects Registration Board
- Board of Architects of Queensland
Northern Territory Architects Boardnot yetArchitects Registration Board of Victorianot yetRegistered Design Practitioner NSWnot yet
Configuration
The package works out-of-the-box with the standard CSV format, but supports custom configuration:
from reggie import RegistrationProcessor, ProcessingConfig
# For different CSV formats, customize the configuration
config = ProcessingConfig(
# If your CSV has different column names:
column_names=["email", "name", "linkedin", "body", "number", "state"],
email_column="email",
full_name_column="name",
# Processing options:
check_registrations=True, # Set to False to skip web scraping
selenium_headless=True, # Set to False to see browser window
output_format="json"
)
processor = RegistrationProcessor(config=config)
Development
See CONTRIBUTING.md for development setup and guidelines.
License
MIT License - see LICENSE file for details.
Metadata
Release files for arch-reggie 0.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 | Provenance | |
|---|---|---|---|---|
| arch_reggie-0.2.0.tar.gz | 1.2 MB | With provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| arch_reggie-0.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.2 MB
Release files / arch_reggie-0.2.0.tar.gz
| Download URL | arch_reggie-0.2.0.tar.gz |
|---|---|
| Size | 1.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a8b45102fc1594b38a9c6112a43c8777c4e6575ed2419c429ec53e418f7f3865
|
|
BLAKE2b-256 checksum How to use checksums |
4b2f7654d5ffbc92ea7a7771ae2295a39be8084b089dd405e402501d0a1ea32e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 6, 2026.
Transparency logRelease files / arch_reggie-0.2.0-py3-none-any.whl
| Download URL | arch_reggie-0.2.0-py3-none-any.whl |
|---|---|
| Size | 19.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
de1f672e4e0b1ed58d9cd6b62c1d10157c6f09b93799cc656d232d8c91507d92
|
|
BLAKE2b-256 checksum How to use checksums |
ff54448cf4e06d3f9fe97c8a77f8755add82820498d193e5cd4d1009766f6ec8
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 6, 2026.
Transparency logSecurity for arch-reggie 0.2.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 arch_reggie-0.2.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 Aug 6, 2026.
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.