Description
The public repository deepseek-ai/deepseek-harness is not currently indexed by OSS Insight.
The repository was created on August 13, 2026 at 11:56 UTC and has been generating a high volume of public GitHub events since then. However, OSS Insight still does not return repository metadata or activity data for it.
Steps to reproduce
- Open the DeepSeek organization analysis page:
https://ossinsight.io/analyze/deepseek-ai#overview
- Search the repository selector for
deepseek-harness.
- Open the repository analysis URL directly:
https://ossinsight.io/analyze/deepseek-ai/deepseek-harness
- Query the public stargazer history endpoint:
https://api.ossinsight.io/v1/repos/deepseek-ai/deepseek-harness/stargazers/history/?per=day&from=2026-08-13&to=2026-08-17
Actual behavior
deepseek-harness is absent from the organization repository selector.
- The direct analysis page only shows generic metadata and does not load the repository's stars, forks, language, or activity metrics.
- The stargazer history API returns a successful response with an empty
rows array.
- The OSS Insight organization page reports 32 public repositories for
deepseek-ai, while the GitHub organization currently has 36 public repositories.
Expected behavior
OSS Insight should recognize deepseek-ai/deepseek-harness, include it in the organization's repository selector, and expose its public GitHub activity through the analysis page and API.
Additional evidence
As checked on August 17, 2026:
This suggests that the repository is publicly visible and actively generating events, but has not yet been discovered or registered by the OSS Insight repository metadata pipeline.
Please let me know if any additional reproduction details would be useful. Thank you.
Description
The public repository
deepseek-ai/deepseek-harnessis not currently indexed by OSS Insight.The repository was created on August 13, 2026 at 11:56 UTC and has been generating a high volume of public GitHub events since then. However, OSS Insight still does not return repository metadata or activity data for it.
Steps to reproduce
https://ossinsight.io/analyze/deepseek-ai#overview
deepseek-harness.https://ossinsight.io/analyze/deepseek-ai/deepseek-harness
https://api.ossinsight.io/v1/repos/deepseek-ai/deepseek-harness/stargazers/history/?per=day&from=2026-08-13&to=2026-08-17
Actual behavior
deepseek-harnessis absent from the organization repository selector.rowsarray.deepseek-ai, while the GitHub organization currently has 36 public repositories.Expected behavior
OSS Insight should recognize
deepseek-ai/deepseek-harness, include it in the organization's repository selector, and expose its public GitHub activity through the analysis page and API.Additional evidence
As checked on August 17, 2026:
WatchEventandForkEventactivity:https://api.github.com/repos/deepseek-ai/deepseek-harness/events
This suggests that the repository is publicly visible and actively generating events, but has not yet been discovered or registered by the OSS Insight repository metadata pipeline.
Please let me know if any additional reproduction details would be useful. Thank you.