AttackMap ATProto Analyzer
attackmap-analyzer-atproto is a thin protocol-aware overlay analyzer for AttackMap.
It is designed to enrich Node/TypeScript service scans (such as node-service) with
AT Protocol-specific exposure signals:
- protocol namespaces:
com.atproto.*,app.bsky.*,chat.bsky.*,tools.ozone.*, plus any third-party authority declared by the repo's own lexiconids (e.g.sh.tangled.*) - lexicon-inferred XRPC endpoint surface. Only
defs.mainof typequery(→GET),procedure(→POST) orsubscription(→WS) is an endpoint;record,objectand defs-only lexicons are not. - XRPC handler registrations (
server.method(nsid, …), generatedserver.<nsid>({ auth, handler })) with their per-endpoint auth:- a configured
auth:verifier is anatproto_auth:route_verifier:<nsid>AuthHint - a handler with no verifier, or an optional one (
*Optional*,nullCreds), is markedatproto_route_auth:anonymous:<nsid>(a ProtocolHint, so core never counts it as an auth control). Core'sRoutemodel has no auth field yet.
- a configured
- protocol auth/signing/identity hints (
did:plc/ PLC directory,@atproto/cryptoand signing/verification APIs; not the bare words "sign", "verify" or "plc") process.env.*secret references (not arbitrary quoted constants)- event stream/subscription exposure hints
- service notes that complement service-level analyzers
This module is heuristic and intentionally lightweight.
detect() fires on a lexicons/ directory, an @atproto/* (or @did-plc/*) dependency in any package.json, a lexicon document under a lexicons/ path, a quoted NSID under a known authority, or an /xrpc/<nsid> URL in JS/TS source. Lockfiles (package-lock.json, npm-shrinkwrap.json) and AttackMap's own report files are never read. Other JSON files are only read to recognize lexicon documents.
Install
uv tool install attackmap --with attackmap-analyzer-atproto # from PyPI
# or: pip install attackmap-analyzer-atproto (installs attackmap too)
# or from source:
pip install git+https://github.com/mlaify/attackmap-analyzer-atproto.git
Usage
attackmap analyze /path/to/repo --module node-service --module atproto
Metadata
Release files for attackmap-analyzer-atproto 0.2.1
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 |
|---|---|---|---|---|
| attackmap_analyzer_atproto-0.2.1.tar.gz | 19.4 kB | With provenance | Details for attackmap_analyzer_atproto-0.2.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| attackmap_analyzer_atproto-0.2.1-py3-none-any.whl | Python 3 | none | any | Details for attackmap_analyzer_atproto-0.2.1-py3-none-any.whl |
Total release size: 32.1 kB
Release files / attackmap_analyzer_atproto-0.2.1.tar.gz
| Download URL | attackmap_analyzer_atproto-0.2.1.tar.gz |
|---|---|
| Size | 19.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
791127cd1c6f49b9a36893d3a32701d5749633821c71eeefbd2655a7f381c41a
|
|
BLAKE2b-256 checksum How to use checksums |
c2bb18f4964812a856ddea3bca3105e78128d2df87606bf7628142060c19e30a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 14, 2026.
Transparency logRelease files / attackmap_analyzer_atproto-0.2.1-py3-none-any.whl
| Download URL | attackmap_analyzer_atproto-0.2.1-py3-none-any.whl |
|---|---|
| Size | 12.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
66d5f1171bf2a3e0cbf1691108ef421c9b5e53e66b9aa87ade822ce6ba5653ea
|
|
BLAKE2b-256 checksum How to use checksums |
5502f6b89edb848ec1769cbd695cd8aafaf9a7504812738fdd315d87269deade
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 Nov 14, 2026.
Transparency logSecurity for attackmap-analyzer-atproto 0.2.1
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
Both files in this release have been uploaded with provenance metadata.
Attestation for attackmap_analyzer_atproto-0.2.1.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 Nov 14, 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.
To learn more about protecting yourself from malicious actors, visit our package security documentation.