atsphinx-typst

v0.1.1 suspicious
4.0
Medium Risk

Generate Typst sources and PDF from Sphinx document.

🤖 AI Analysis

Final verdict: SUSPICIOUS

The package appears generally benign with low risks in network, shell, and obfuscation categories. However, the incomplete maintainer profile raises concerns about its origin and long-term maintenance.

  • Incomplete maintainer profile
  • Metadata risk score of 3 out of 10
Per-check LLM notes
  • Network: No network calls detected, which is normal for most Python packages unless they require external services.
  • Shell: No shell execution patterns detected, indicating the package does not execute system commands.
  • Obfuscation: No obfuscation patterns detected in the package.
  • Credentials: No credential harvesting patterns detected in the package.
  • Metadata: The maintainer has an incomplete profile and may be new or inactive, raising some suspicion but not conclusive evidence of malice.

📦 Package Quality Overall: Medium (6.2/10)

✦ High Test Suite 9.0

Test suite present — 13 test file(s) found

  • Test runner config found: conftest.py
  • 13 test file(s) detected (e.g. conftest.py)
✦ High Documentation 9.0

Well-documented package

  • Documentation URL: "Documentation" -> https://atsphinx.github.io/typst
  • 1 documentation file(s) (e.g. conf.py)
  • Detailed PyPI description (1014 chars)
  • Classifier: Documentation
○ Low Contributing Guide 2.0

No contributing guide or governance files found

  • No CONTRIBUTING, CODE_OF_CONDUCT, or governance files found
◈ Medium Type Annotations 5.0

Partial type annotation coverage

  • 57 type-annotated function signatures detected in source
◈ Medium Multiple Contributors 6.0

Limited contributor diversity

  • 2 unique contributor(s) across 100 commits in atsphinx/typst
  • Two distinct contributors found

🔬 Heuristic Checks

Outbound Network Calls

No suspicious network call patterns found

Code Obfuscation

No obfuscation patterns detected

Shell / Subprocess Execution

No shell execution patterns detected

Credential Harvesting

No credential harvesting patterns detected

Typosquatting

No typosquatting candidates detected

Registered Email Domain

Email domain looks legitimate: attakei.net>

Suspicious Page Links

All external links appear legitimate

Git Repository History

Repository atsphinx/typst appears legitimate

Maintainer History score 4.0

2 maintainer concern(s) found

  • Author name is missing or very short
  • Author "" appears to have only 1 package on PyPI (new or inactive account)
Known CVE Vulnerabilities

No known vulnerabilities found in OSV database.

💡 AI App Starter Prompt

Use this prompt to build a project with atsphinx-typst
Create a Python-based mini-application that leverages the 'atsphinx-typst' package to convert Sphinx documentation into Typst source files and subsequently generate PDF outputs. This application will serve as a streamlined tool for developers and technical writers who wish to publish their Sphinx-generated documentation in a more visually appealing format suitable for print and digital distribution.

The application should include the following core functionalities:
1. **Sphinx Document Conversion**: Integrate the ability to take existing Sphinx documentation files (RST format) and convert them into Typst source files. This process should preserve the structure, styling, and content of the original documents as closely as possible.
2. **Typst Source Customization**: Allow users to customize the Typst template used for conversion. This could include changing fonts, colors, and layout options to better suit the user's needs.
3. **PDF Generation**: After converting the documents to Typst source files, the application should automatically compile these into PDF files using Typst's compiler. Ensure that the generated PDFs are high-quality and ready for printing.
4. **Batch Processing**: Implement a feature that allows users to select multiple Sphinx documentation files and convert/process them in bulk, saving time for users working with large projects.
5. **Preview Functionality**: Include a preview option where users can see a live preview of the Typst source file before finalizing the PDF generation. This will help in ensuring the accuracy and aesthetic appeal of the final output.
6. **Output Management**: Provide options for managing the output files, such as choosing the directory for storing the Typst source files and PDF outputs, renaming files, and archiving completed projects.

To achieve these functionalities, you will need to utilize the 'atsphinx-typst' package effectively. Specifically, focus on how to integrate the package's capabilities for generating Typst sources and compiling them into PDFs within your application. Additionally, consider how you can extend the package's features to include customization options and batch processing support.

This project aims to provide a powerful yet user-friendly tool for enhancing the readability and accessibility of technical documentation, making it easier for teams to share and distribute their work in professional formats.

💬 Discussion Feed

Leave a comment

No discussion yet. Be the first to share your thoughts!