pynakes
pynakes is a reference management engine for BibTeX and BibLaTeX bibliographies and their research materials, exposed through a Python library and CLI.
Acquire and curate references, compare and enrich records, organize groups,
track citations in manuscripts, and optionally manage PDFs and source bundles
through Pinax, addressed by citation key. The .bib remains authoritative,
and JabRef interoperability keeps existing libraries usable across tools.
Release preparation: this checkout targets pynakes 0.7.0 Beta and the VS Code editor 0.1.0 Alpha, neither published yet. The Python API is experimental until 1.0; the 0.7 CLI, JSON envelope, and error codes follow the compatibility policy. See the release checklist for remaining gates.
What it offers
- Source preservation. Untouched entries write back byte-for-byte. Surgical edits keep diffs focused; whole-file formatting is an explicit operation.
- Review before writing. Preview changes with
--dry-run --diff. Writes are atomic and re-parse-validated, backups are optional, and ambiguous operations report conflicts rather than guessing. - Reference management. Import, search, lint, normalize, deduplicate, edit, convert, and export references. Track TeX citations and prepare scrubbed public copies without altering the working library.
- References and materials together. Pinax tracks PDFs, source bundles, and provenance. Materials can follow entries through citation-key changes and bibliography combine/split operations.
- Research reads. Compare a set of papers through bounded, paged reads of
their abstracts, materials, and recorded provenance; save selections as named
queries; describe a library's coverage with
analyze; and map its co-author network withcoauthors. - Automation. Structured JSON, change plans, exit codes, and machine-readable capabilities support scripts, CI, and agent workflows. Network access is explicit.
Install
Requires Python 3.12+ on Linux, macOS, or Windows. Install the published release with:
pip install pynakes
Or install the CLI as an isolated tool with uv:
uv tool install pynakes
For this development checkout and optional tooling, see the installation guide.
Quick start
This offline example creates a bibliography and previews an edit before applying it:
pynakes init refs.bib
pynakes ref add refs.bib Newton1687 --type book --field author="Isaac Newton" --field title="Principia" --field year=1687 --field publisher="Royal Society"
pynakes inspect refs.bib --json
pynakes ref edit refs.bib Newton1687 --field note="Reviewed" --dry-run --diff
# Apply after reviewing the diff:
pynakes ref edit refs.bib Newton1687 --field note="Reviewed"
pynakes search refs.bib Principia --json
When the current directory has exactly one .bib file, single-library commands
can infer its path. Otherwise, provide the file explicitly. See the
quick-start guide
for imports, normalization, and other workflows.
The Python library uses the same staged lifecycle:
from pynakes import Bibliography, CanonicalLayout
bib = Bibliography.open("refs.bib")
bib.format(CanonicalLayout(field_order="preferred", wrap_values="stable"))
print(bib.diff())
# Commit after reviewing the diff:
bib.commit(backup=True)
See the API reference
for preview(), change_plan(), and the other library operations.
VS Code editor
The editor companion provides a bibliography table, entry and metadata editing, groups, citation navigation, and material access using the same engine. It is a project-scoped editor, currently an unpublished alpha. Its user guide and build instructions are maintained separately.
Documentation
- Usage and commands
- Pinax: references and their materials
- Metadata settings
- JabRef compatibility
- Network and privacy
- Automation and JSON contract
- Git workflows and CI
- Architecture
The planned Library and rebuildable Catalogue APIs extend this engine to
collection-wide work; they are not implemented yet. See the
vision and
development plan.
Release history is in the changelog.
Contributing and license
See CONTRIBUTING.md for development setup and checks. Licensed under MIT.
Named after the Pinakes, Callimachus’s catalogue of the Library of Alexandria.
A .bib is the index card; a pinax is the card together with the shelf it points at.
Metadata
Release files for pynakes 0.8.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 | Actions |
|---|---|---|---|---|
| pynakes-0.8.0.tar.gz | 1.8 MB | With provenance | Details for pynakes-0.8.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| pynakes-0.8.0-py3-none-any.whl | Python 3 | none | any | Details for pynakes-0.8.0-py3-none-any.whl |
Total release size: 3.5 MB
Release files / pynakes-0.8.0.tar.gz
| Download URL | pynakes-0.8.0.tar.gz |
|---|---|
| Size | 1.8 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7f723a738cd9261e4f6b8f52e1e473d2643722864beee4ce16b88590ea7df1df
|
|
BLAKE2b-256 checksum How to use checksums |
c1470eeda2cd1f94fcb98429954beedac0fd8071dce0462995b4b2def2192c9e
|
| 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 Oct 22, 2026.
Transparency logRelease files / pynakes-0.8.0-py3-none-any.whl
| Download URL | pynakes-0.8.0-py3-none-any.whl |
|---|---|
| Size | 1.7 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2536cea018313471850e9621e2a6f057c72b9eb994ae547419cddb6804b81b66
|
|
BLAKE2b-256 checksum How to use checksums |
11215f8a6cff3f5a39f0a0da82e0cb2fa9f1d90bb7c9bf52d0b436260c4cd928
|
| 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 Oct 22, 2026.
Transparency logSecurity for pynakes 0.8.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
Both files in this release have been uploaded with provenance metadata.
Attestation for pynakes-0.8.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 Oct 22, 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.