microsoft/applicationinspector

A source code analyzer built for surfacing features of interest and other characteristics to answer the question 'What's in the code?' quickly using static...

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 39 minutes ago
Added to GitGenius on September 15th, 2026
Created on October 7th, 2019
Open Issues & Pull Requests: 28 (+0)
GitHub issues: Enabled
Number of forks: 366
Total Stargazers: 4,394 (+0)
Total Subscribers: 77 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 3.9 days
Mean response time: 201.1 days
90th percentile: 764.0 days
Tracked items: 21

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 2
Closed in 7 days: 1
Avg open age: 828 days
Stale 30+ days: 6
Stale 90+ days: 6

Recent activity

Opened in 7 days: 2
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (10)
  • bug (8)
  • rule (3)
  • tests (1)

Detailed Description

Application Inspector is a static source code analyzer that uses a JSON-based rules engine to identify features and characteristics in code.

The tool addresses the need to quickly understand what functionality exists in a codebase without manual review. It works by applying pattern-matching rules defined in JSON format against source code to surface features of interest and other notable characteristics. This approach enables rapid scanning of components to answer fundamental questions about code composition and behavior.

Application Inspector suits teams evaluating third-party components before integration, tracking feature-level changes across versions, or conducting security assessments where understanding code capabilities is essential. It works across multiple programming languages through its rules-based detection system. The tool is particularly valuable in supply chain security contexts where you need to verify what a component actually does before bringing it into your project.

The project shows consistent maintenance with regular updates addressing bug fixes and rule improvements. Development activity demonstrates responsiveness to user-reported issues and ongoing refinement of the detection rules that form the core of the tool's functionality.