rlidwka/sinopia
Sinopia
Sinopia ist ein privater npm-Registry-Server zum Hosten, Verwalten und Verteilen privater Pakete und Scoped-Module innerhalb eines internen Netzwerks. Er fungiert als privater Paketmanager, der den Zugriff auf internen Code durch Benutzerauthentifizierung und verschlüsselte Tokens steuert.
Das System bietet eine Caching-Schicht, die öffentliche Registry-Pakete lokal speichert, um Bandbreite zu sparen und Installationsgeschwindigkeiten zu verbessern. Es enthält zudem eine webbasierte Oberfläche zum Erkunden von Paketen, Einsehen der Dokumentation und Verwalten des Registry-Status.
Das Projekt deckt ein breites Spektrum an Paketmanagement-Funktionen ab, darunter das Proxying von Remote-Repositories, die Verteilung von Scoped-Paketen und die Möglichkeit, öffentliche Pakete durch lokale Versionen zu überschreiben. Der Zugriff wird über ein erweiterbares Autorisierungssystem und Benutzerrechteverwaltung gesteuert, während die Kommunikation durch Verkehrsverschlüsselung gesichert ist.
Features
- npm Registry Deployments - Hosts and manages private npm registries for distributing internal packages within a network.
- Registry Proxies - Acts as a single point of access by proxying metadata and tarballs from external registries.
- Upstream Proxy Caching - Caches remote registry packages locally to reduce latency and ensure availability during upstream outages.
- Proxy Caches - Fetches metadata and tarballs from remote uplinks to cache external packages locally.
- Private Package Registries - Controls the distribution of internal software packages using authentication tokens and granular permissions.
- Scoped - Provides the ability to host and distribute packages organized by organization-specific scopes.
- Registry Proxies - Serves as a network intermediary between local environments and public registries for failover and overrides.
- Access Control and Authorization - Implements a modular system for enforcing granular user permissions and access rules for packages.
- User Account Management - Handles user registration and identity management to control package access and publishing rights.
- Permission-Based Access Control - Manages user credentials and defines specific permissions to control who can access or publish packages.
- Token Authentication - Issues encrypted tokens for user authentication to avoid storing persistent credentials on clients.
- Token-Based Authentication - Uses encrypted session tokens to verify user identity and authorize requests without persistent credentials.
- Local Package Caches - Provides local disk caching of package archives to speed up installation and reduce network traffic.
- Package Overrides - Serves locally published versions of third-party packages to apply custom fixes or forks.
- Package Caches - Maintains local copies of public registry packages to accelerate installation and save bandwidth.
- Registry Management Interfaces - Ships a visual browser for exploring packages, viewing documentation, and managing registry state.
- Registry Explorers - Provides a web-based interface for browsing stored packages and managing the registry state.
- TLS Traffic Encryption - Secures communication channels between the npm client and the registry server using SSL/TLS encryption.
- Scoped Package Mapping - Supports organizational naming conventions by grouping packages into namespaces to separate internal and third-party code.
- Registry Explorers - Ships a visual web interface for exploring hosted packages and managing the server state.
- Node.js Frameworks and Tools - Private NPM registry server.
