apple/swift-log

A Logging API for Swift

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 2 minutes ago
Type:Library / SDKCategory(s):Core & Utility LibrariesLanguages & Runtimes
Added to GitGenius on September 17th, 2026
Created on February 11th, 2019
Open Issues & Pull Requests: 26 (+0)
GitHub issues: Enabled
Number of forks: 344
Total Stargazers: 4,050 (+0)
Total Subscribers: 55 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 21.5 hours
Mean response time: 134.7 days
90th percentile: 127.7 days
Tracked items: 53

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 14
New in 7 days: 3
Closed in 7 days: 3
Avg open age: 456 days
Stale 30+ days: 12
Stale 90+ days: 4

Recent activity

Opened in 7 days: 3
Closed in 7 days: 3
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • kind/enhancement (4)
  • kind/support (4)
  • good first issue (2)
  • 🆕 semver/minor (2)
  • area/documentation (1)
  • platform/android (1)
  • platform/windows (1)
  • semver/none (1)

Detailed Description

swift-log is a logging API for Swift that provides a unified, performant, and ergonomic interface for logging across the Swift ecosystem.

The tool solves the problem of fragmented logging approaches in Swift libraries and applications by offering a standardized API that libraries can adopt without imposing a specific logging backend on their users. It works as an abstraction layer: applications choose which concrete logging backend implementation to use, while libraries depend only on the API itself. This separation allows different parts of a Swift ecosystem to coexist without logging conflicts or duplicate dependencies.

Developers should adopt swift-log if they are building libraries that need logging capabilities or applications that want to standardize logging across multiple dependencies. It suits any Swift project where you want to decouple the logging interface from the implementation details. The tool is explicitly positioned as an API package, meaning you must select a community-maintained logging backend for production use rather than relying on a built-in implementation. The Swift Package Index provides a searchable collection of available backends to help with this choice.

The project maintains both Swift Package Manager and CMake build support, with SPM as the primary development system and CMake available for integrated or mixed build environments. Testing is managed exclusively through Swift Package Manager.