‹ Reports
The Dispatch

OSS Report: public-apis/public-apis

API Integrity Concerns Rise as Public APIs Repository Faces Multiple Reports of Compromised Services

The Public APIs repository, a community-curated collection of free APIs across various domains, has seen a surge in issues related to compromised and outdated APIs, raising concerns about the reliability of its listings. This project, maintained with contributions from the community and professionals associated with APILayer, serves as a vital resource for developers integrating external data into their applications.

Recent Activity

Recent issues highlight a growing concern over the integrity of API listings. Notable issues include #3984 (Pixel Encounter API), #3987 (xMath API), and #3977 (AniApi), all indicating compromised or outdated services. This pattern suggests an urgent need for enhanced monitoring and updating processes to maintain the repository's reliability.

Development Team and Recent Activity

  1. Matheus Felipe (matheusfelipeog)

    • Removed broken APIs and added new ones like "Free Url Shortener" and "National Park Service".
    • Last commit: 45 days ago.

  2. APILayer (apilayer-admin)

    • Updated README.md and collaborated on API additions/removals.
    • Last commit: 45 days ago.

  3. FayeNichols

    • Added APIs such as "Hirak OCR" and "Hirak FaceAPI".
    • Last commit: 45 days ago.

  4. Zaldy Pagaduan Jr. (zopagaduanjr)

    • Contributed "PRC Exam Schedule" API.
    • Last commit: 45 days ago.

  5. Diego Parrilla (diegoparrilla)

    • Added "Threat Jammer" to Security category.
    • Last commit: 45 days ago.

  6. Kyle Calica (stcalica)

    • Worked on redesign elements for Postman logos.
    • Last active: 186 days ago.

The team is actively engaged in maintaining the repository, focusing on quality by removing non-functional APIs and adding new resources across diverse categories.

Of Note

  1. High Volume of Open PRs: With 316 open pull requests, there may be bottlenecks in review processes affecting timely updates.

  2. Inactive Merges: Some PRs remain unmerged despite meeting guidelines, indicating potential prioritization issues.

  3. Community Engagement: Contributors are eager for collaboration but may face frustration due to delayed responses from maintainers.

  4. Quality Control: While many contributions adhere to guidelines, some older PRs lack attention to detail, potentially affecting quality.

  5. Closed PRs: Some submissions do not meet requirements or are unnecessary, indicating a need for stringent review processes.

Quantified Reports

Quantify Issues



Recent GitHub Issues Activity

Timespan Opened Closed Comments Labeled Milestones
7 Days 2 0 0 2 1
30 Days 7 0 2 7 1
90 Days 23 6 8 23 1
1 Year 110 94 56 102 1
All Time 605 587 - - -

Like all software activity quantification, these numbers are imperfect but sometimes useful. Comments, Labels, and Milestones refer to those issues opened in the timespan in question.

Quantify commits



Quantified Commit Activity Over 30 Days

Developer Avatar Branches PRs Commits Files Changes
Adam Ross (R055A) 0 0/0/2 0 0 0
None (HugoW5) 0 1/0/0 0 0 0
None (mdc004) 0 1/0/0 0 0 0
lvwzhen (lvwzhen) 0 1/0/0 0 0 0
Arnav Parashar (Arnav100) 0 1/0/0 0 0 0
None (donutz03) 0 1/0/0 0 0 0
Marc Prud'hommeaux (marcprux) 0 1/0/0 0 0 0
None (Nodebaron) 0 1/0/0 0 0 0
Sarwar Hossain (Sarwar242) 0 1/0/0 0 0 0
None (bacloud23) 0 1/0/0 0 0 0
Chris Wangsanata (cwangsanata) 0 1/0/0 0 0 0
None (sunilnemani) 0 2/0/2 0 0 0
Jacob Brewer (Jacobbrewer1) 0 4/0/2 0 0 0
Abhinayadanda (Abhinayadanda) 0 1/0/0 0 0 0
Jordan Prescott (Jordan-Prescott) 0 1/0/0 0 0 0
CaptainBeast (ShadowEmperorYT) 0 1/0/0 0 0 0
Stuart John Atkinson (StuartJAtkinson) 0 1/0/1 0 0 0
Saqib Malik (maliksaqibahmad) 0 1/0/0 0 0 0
Marcos Alves (marcoscavaleiro) 0 1/0/0 0 0 0

PRs: created by that dev and opened/merged/closed-unmerged during the period

Detailed Reports

Report On: Fetch issues



Recent Activity Analysis

The recent activity in the Public APIs repository indicates a growing concern over the functionality and reliability of several APIs listed, with 18 open issues currently. Notably, there are multiple reports of compromised or outdated APIs, including #3984 (Pixel Encounter API), #3987 (xMath API), and #3977 (AniApi). This trend highlights a significant issue with maintaining the integrity of the API listings, as users are reporting security risks and broken links. The presence of multiple issues related to deprecated services suggests a need for more rigorous monitoring and updating of the repository to ensure that it remains a trustworthy resource for developers.

Issue Details

Recently Created Issues

  1. Issue #3988: connecation timeout

    • Priority: Low
    • Status: Open
    • Created: 4 days ago

  2. Issue #3987: xMath API link is outdated

    • Priority: Medium
    • Status: Open
    • Created: 6 days ago

  3. Issue #3984: Pixel Encounter API is compromised

    • Priority: High
    • Status: Open
    • Created: 8 days ago

  4. Issue #3981: Josué

    • Priority: Low
    • Status: Open
    • Created: 13 days ago

  5. Issue #3977: AniApi Compromised

    • Priority: High
    • Status: Open
    • Created: 16 days ago
    • Updated: 13 days ago

Recently Updated Issues

  1. Issue #3969: Best APIs

    • Priority: Low
    • Status: Open
    • Created: 24 days ago
    • Updated: 7 days ago

  2. Issue #3887: Google maps link

    • Priority: Low
    • Status: Open
    • Created: 81 days ago
    • Updated: 7 days ago

  3. Issue #3963: API

    • Priority: Low
    • Status: Open
    • Created: 30 days ago

  4. Issue #3959: Mohamedgamal

    • Priority: Low
    • Status: Open
    • Created: 39 days ago

  5. Issue #3952: Is AniAPI still available?

    • Priority: Medium
    • Status: Open
    • Created: 52 days ago

The issues indicate a pattern of users reporting not only broken links but also security concerns regarding certain APIs, which could undermine user trust in the repository's reliability as a resource for developers.

Report On: Fetch pull requests



Overview

The public-apis repository currently has 316 open pull requests (PRs) and 2,915 closed PRs. The recent activity shows a mix of new API additions, updates to existing entries, and corrections to broken links or descriptions.

Summary of Pull Requests

  1. PR #3993: Add The Dobby Club API
    Created by Jordan Prescott, this PR adds the Dobby Club API to the Video category. It follows all contribution guidelines and is a recent addition.

  2. PR #3992: Refactor
    Submitted by donutz03, this PR refactors the validation script for formatting. It includes additional lines of code aimed at improving the repository's structure.

  3. PR #3991: Update README.md
    Saqib Malik fixed numerous typos and grammatical errors in the README file, enhancing readability and professionalism.

  4. PR #3986: Added Klaviyo API
    Arnav Parashar introduced the Klaviyo API, which is designed for data-driven marketing automation.

  5. PR #3982: Fixed broken link to Postnord Api
    HugoW5 corrected a broken link in the README, ensuring users can access the correct PostNord API documentation.

  6. PR #3980: Add Safe-Text API
    This PR by bacloud23 adds the Safe-Text API to the Text Analysis category, contributing to the diversity of APIs available.

  7. PR #3979: Update README.md
    Nodebaron added OpenWeatherMap API under the Weather category, enhancing the repository's offerings in weather-related APIs.

  8. PR #3978: Remove AniAPI
    Chris Wangsanata proposed removing AniAPI from the list due to its unavailability.

  9. PR #3976: feat(f1-data): Adding the f1 data API
    Jacob Brewer introduced an F1 data API, contributing to sports-related data offerings.

  10. PR #3973: WhatsApp Profile Info
    Marcos Alves added a new API that provides profile information from WhatsApp numbers.

  11. PR #3972: Updated link to contribution.md
    Abhinayadanda updated a link in the PULL_REQUEST_TEMPLATE.md file for better accessibility.

  12. PR #3971: Update fawazahmed0/currency-api to fawazahmed0/exchange-api
    Marc Prud'hommeaux updated a link in the README to reflect a change in repository ownership.

  13. PR #3970: Added BitSkins API to Games & Comics
    CaptainBeast contributed a new API for obtaining information about CS2 and Dota skins.

  14. PR #3968: Add SWAPI API
    mdc004 added SWAPI, expanding entertainment-related APIs.

  15. PR #3967: Add OpenL Translate to Text Analysis
    lvwzhen contributed an AI translation service that supports over 100 languages.

  16. PR #3966: feat(docs): Adding the golf data API
    Jacob Brewer added a golf data API, further diversifying sports-related APIs.

  17. PR #3965: Added new test file
    Sarwar Hossain introduced a new test file for validation purposes.

  18. PR #3962: Add Zuplo to Development
    Adrian Machado added Zuplo as an API management platform.

  19. PR #3961: Added onlypepes API
    Ismael Bautista contributed an API for random Pepe memes.

  20. PR #3958: Add HTTPHive API
    Melissa Longenberger added HTTPHive.com to the Animals category.

Analysis of Pull Requests

The current state of pull requests in the public-apis repository indicates active engagement from contributors with a focus on enhancing and maintaining the quality of the repository's content. A notable trend is the consistent addition of new APIs across various categories such as Video, Text Analysis, Sports, and Weather, reflecting ongoing interest in diverse data sources among developers.

The recent PRs show a balanced mix of new additions and maintenance tasks such as fixing broken links or updating outdated information (e.g., PRs like #3982 and #3978). This suggests that contributors are not only focused on expanding the repository but also on ensuring that existing entries remain functional and relevant.

However, there are some anomalies worth noting:

  1. High Volume of Open PRs: With 316 open pull requests, there may be potential bottlenecks in review processes or merge activities that could hinder timely updates.

  2. Inactive Merges: Several recent PRs have not been merged despite meeting contribution guidelines (e.g., PRs like #3990 and others). This could indicate either resource constraints or prioritization issues within maintainers' workflows.

  3. Community Engagement: The presence of comments from contributors seeking merges (like Adrian Machado's comments on PR #3962) highlights an eagerness within the community for collaboration but may also point towards frustration with delays in response times from maintainers.

  4. Quality Control: While many contributions adhere strictly to formatting guidelines, some older PRs show less attention to detail regarding descriptions or formatting (e.g., PRs like #3929), which could affect overall quality if not addressed during reviews.

  5. Closed PRs: The closed pull requests indicate that while many contributors are eager to add value, some submissions do not meet requirements or are deemed unnecessary (e.g., PRs involving broken links or inactive APIs).

In conclusion, while there is vibrant activity within this repository with numerous contributions enhancing its value as a resource for developers, attention must be paid to managing open pull requests effectively and ensuring timely merges to maintain community enthusiasm and trust in project stewardship.

Report On: Fetch commits



Repo Commits Analysis

Development Team and Recent Activity

Team Members and Activities

  1. APILayer (apilayer-admin)

    • Recent activity includes multiple updates to the README.md file, with the most recent commit 45 days ago.
    • Collaborated with various contributors on API additions and removals.

  2. Matheus Felipe (matheusfelipeog)

    • Active in maintaining the repository by removing broken APIs and adding new ones. Notably removed multiple APIs that returned errors (HTTP 404, 503).
    • Contributed to adding new APIs across various categories, such as "Free Url Shortener" and "National Park Service".
    • His last commit was 45 days ago, indicating ongoing contributions.

  3. Kyle Calica (stcalica)

    • Contributed to a significant merge that included redesign elements for Postman logos and improved API categorization.
    • Last active 186 days ago.

  4. FayeNichols

    • Added several APIs related to text analysis and machine learning, including "Hirak OCR" and "Hirak FaceAPI".
    • Last activity recorded 45 days ago.

  5. Zaldy Pagaduan Jr. (zopagaduanjr)

    • Contributed the "PRC Exam Schedule" API to the Government category.
    • Last active 45 days ago.

  6. Diego Parrilla (diegoparrilla)

    • Added "Threat Jammer" to the Security category.
    • Last active 45 days ago.

  7. Others: Several other contributors have made minor contributions or opened pull requests, but their activities are less frequent or not as impactful as those listed above.

Patterns and Themes

  • Active Maintenance: The repository shows consistent activity with regular updates, particularly from Matheus Felipe, who is heavily involved in both adding new APIs and removing broken ones.
  • Collaborative Contributions: Many contributors are working together on similar tasks, such as API additions and documentation improvements.
  • Focus on Quality: The team is actively removing non-functional APIs, indicating a commitment to maintaining a high-quality resource for users.
  • Diverse Contributions: Contributions span various domains, showcasing the repository's extensive reach and utility across different areas of development.

Conclusion

The development team is actively engaged in maintaining and enhancing the Public APIs repository. The focus on quality through the removal of broken links and the addition of new resources reflects a strong commitment to providing a valuable tool for developers. The collaborative nature of contributions suggests a healthy community around this project.