Pros of waka-readme-stats

• More comprehensive statistics, including language breakdown and coding activity
• Customizable themes and layout options
• Supports multiple version control platforms (GitHub, GitLab, Bitbucket)

Cons of waka-readme-stats

• More complex setup process
• Requires more configuration and maintenance
• Potentially slower update times due to increased data processing

Code Comparison

waka-readme:

name: Waka Readme

on:
  schedule:
    - cron: '0 0 * * *'

jobs:
  update-readme:
    name: Update Readme with Metrics
    runs-on: ubuntu-latest
    steps:
      - uses: athul/waka-readme@master
        with:
          WAKATIME_API_KEY: ${{ secrets.WAKATIME_API_KEY }}

waka-readme-stats:

name: Waka Readme

on:
  schedule:
    - cron: '30 18 * * *'
  workflow_dispatch:
jobs:
  update-readme:
    name: Update Readme with Metrics
    runs-on: ubuntu-latest
    steps:
      - uses: anmol098/waka-readme-stats@master
        with:
          WAKATIME_API_KEY: ${{ secrets.WAKATIME_API_KEY }}
          GH_TOKEN: ${{ secrets.GH_TOKEN }}
          SHOW_OS: "True"
          SHOW_PROJECTS: "True"

The waka-readme-stats configuration offers more options for customization and data display, while waka-readme has a simpler setup with fewer configuration options.

Pros of wakapi

• Self-hosted solution, offering more control over data and privacy
• Provides a web interface for viewing statistics and generating reports
• Supports multiple users and organizations

Cons of wakapi

• Requires more setup and maintenance compared to waka-readme
• May have higher resource requirements due to self-hosting

Code comparison

waka-readme:

name: Waka Readme

on:
  schedule:
    - cron: '0 0 * * *'
  workflow_dispatch:
jobs:
  update-readme:
    name: Update Readme with Metrics
    runs-on: ubuntu-latest
    steps:
      - uses: athul/waka-readme@master
        with:
          WAKATIME_API_KEY: ${{ secrets.WAKATIME_API_KEY }}

wakapi:

func (api *APIClient) GetSummary(start, end time.Time) (*Summary, error) {
    url := fmt.Sprintf("%s/api/summary?start=%s&end=%s", api.BaseURL, start.Format(time.RFC3339), end.Format(time.RFC3339))
    req, err := http.NewRequest("GET", url, nil)
    if err != nil {
        return nil, err
    }
    // ... (additional code)
}

The waka-readme example shows a GitHub Actions workflow configuration, while the wakapi example demonstrates a Go function for retrieving summary data from the API. This reflects the different approaches of the two projects: waka-readme focuses on GitHub integration, while wakapi provides a more comprehensive self-hosted solution with its own API.

Pros of waka-box

• Displays coding stats in a GitHub gist, which can be pinned to your profile
• Provides a visual representation of coding time with bar graphs
• Easier to set up and maintain as it uses GitHub Actions

Cons of waka-box

• Limited customization options for the displayed information
• Requires a separate gist to be created and maintained
• May not update as frequently as waka-readme

Code Comparison

waka-box:

- name: Update gist
  uses: matchai/waka-box@master
  env:
    GH_TOKEN: ${{ secrets.GH_TOKEN }}
    GIST_ID: ${{ secrets.GIST_ID }}
    WAKATIME_API_KEY: ${{ secrets.WAKATIME_API_KEY }}

waka-readme:

- uses: athul/waka-readme@master
  with:
    WAKATIME_API_KEY: ${{ secrets.WAKATIME_API_KEY }}
    GH_TOKEN: ${{ secrets.GH_TOKEN }}
    SHOW_TITLE: true

Summary

Both waka-box and waka-readme are useful tools for displaying WakaTime coding statistics on GitHub profiles. waka-box offers a more visual representation in a pinned gist, while waka-readme provides greater flexibility by updating the README directly. The choice between the two depends on personal preference for display style and desired level of customization.

Pros of github-trends

• Provides more comprehensive GitHub statistics, including language usage and contribution patterns
• Offers customizable visualization options for displaying trends
• Supports multiple time ranges for analyzing GitHub activity

Cons of github-trends

• More complex setup and configuration process
• Requires additional dependencies and API access
• May have higher resource usage due to more extensive data processing

Code Comparison

waka-readme:

import re
import os
import base64
import requests
import datetime
import traceback
from github import Github, GithubException

github-trends:

import os
import requests
import pandas as pd
import matplotlib.pyplot as plt
from github import Github
from dotenv import load_dotenv

Key Differences

• waka-readme focuses specifically on WakaTime integration for coding time statistics
• github-trends provides a broader range of GitHub activity analysis and visualization
• waka-readme has a simpler setup process and fewer dependencies
• github-trends offers more customization options and detailed insights

Use Cases

• Choose waka-readme for quick and easy integration of coding time statistics in your GitHub profile
• Opt for github-trends when you need comprehensive GitHub activity analysis and customizable visualizations

Community and Support

• Both projects have active communities and regular updates
• waka-readme has a larger user base and more contributors
• github-trends offers more extensive documentation and examples

Pros of awesome-github-profile-readme

• Comprehensive collection of creative and inspiring GitHub profile READMEs
• Includes tools, articles, and resources for creating profile READMEs
• Community-driven with a wide variety of examples and styles

Cons of awesome-github-profile-readme

• Requires manual browsing and implementation of ideas
• No automated integration with GitHub profiles
• May be overwhelming due to the large number of examples

Code comparison

waka-readme:

import re
import os
import base64
import requests
from github import Github, InputGitAuthor

def update_readme():
    # Code to update README with WakaTime stats

awesome-github-profile-readme:

# Awesome GitHub Profile README

A curated list of awesome GitHub Profile READMEs

## Categories

- [Tools](#tools)
- [Articles](#articles)
- [Tutorials](#tutorials)

Summary

waka-readme is a focused tool for automatically updating GitHub profile READMEs with WakaTime statistics, while awesome-github-profile-readme is a comprehensive resource for inspiration and guidance on creating unique profile READMEs. waka-readme offers automation but is limited to WakaTime integration, whereas awesome-github-profile-readme provides a wide range of ideas and resources but requires manual implementation.