Neo4j Doc Manager is a tool that will import data in Mongodb for a Neo4j graph structure, via Mongo-Connector.
1 maintainer
Metadata
1 maintainer
Release files for neo4j-doc-manager 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 | |
|---|---|---|---|---|
| neo4j-doc-manager-0.1.2.tar.gz | 6.0 kB | Without provenance | Details |
Release files / neo4j-doc-manager-0.1.2.tar.gz
| Download URL | neo4j-doc-manager-0.1.2.tar.gz |
|---|---|
| Size | 6.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f85d03bc8320c8e05486e2cf8696112bdda9fb9fcefd9ede7071a88cf17231dc
|
|
BLAKE2b-256 checksum How to use checksums |
0d8a4020be33870c346c0ee6f92a142aedbcc914171a7028fad6d0aafe237087
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for neo4j-doc-manager 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.
