{match[5]});
} else if (match[6]) {
parts.push({match[7]});
} else if (match[8]) {
parts.push({match[9]});
}
lastIndex = match.index + match[0].length;
}
if (lastIndex < text.length) parts.push(text.slice(lastIndex));
if (parts.length === 0) return text;
const keyRef = {
current: keyIndex
};
return expandHtmlTags(parts, keyRef);
};
const processBadges = text => {
if (!text || typeof text !== 'string') return text;
if (YES_RE.test(text)) return ✓;
if (NO_RE.test(text)) return ✗;
if (LIMITED_RE.test(text)) return ◐;
if (NA_RE.test(text) || NA2_RE.test(text)) return Not applicable;
return processText(text);
};
const cellClassName = text => {
if (!text || typeof text !== 'string') return undefined;
if (NA_RE.test(text)) return 'yt-cell-na';
if (NA2_RE.test(text)) return 'yt-cell-na2';
return undefined;
};
const expandSimpleTags = (str, keyRef) => {
const result = [];
let last = 0;
SIMPLE_TAG_RE.lastIndex = 0;
let m;
while ((m = SIMPLE_TAG_RE.exec(str)) !== null) {
if (m.index > last) result.push(str.slice(last, m.index));
if (m[1]) {
result.push(); } else if (m[2]) { result.push(
,
); } else if (m[3]) { result.push(Note: ); } else if (m[4]) { result.push(Warning: ); } last = m.index + m[0].length; } if (last < str.length) result.push(str.slice(last)); return result; }; const expandHtmlTags = (chunks, keyRef) => { const out = []; for (const chunk of chunks) { if (typeof chunk === 'string') { out.push(...expandSimpleTags(chunk, keyRef)); } else { out.push(chunk); } } return out; }; const extractText = node => { if (node === null || node === undefined) return ''; if (typeof node === 'string') return node; if (typeof node === 'number') return String(node); if (typeof node === 'boolean') return ''; if (Array.isArray(node)) return node.map(extractText).join(''); if (node && typeof node === 'object' && node.type) { const props = node.props || ({}); if (typeof props.children === 'string') return props.children; if (props.children) return extractText(props.children); return ''; } return String(node || ''); }; const [mounted, setMounted] = useState(false); useEffect(() => { setMounted(true); }, []); const data = useMemo(() => { if (propData) return propData; if (content && typeof content === 'string') return parseYamlTableContent(content); if (!children) return []; if (typeof children === 'string') return parseYamlTableContent(children); const childrenArray = Array.isArray(children) ? children : [children]; return parseYamlTableContent(childrenArray.map(extractText).join('').trim()); }, [children, propData, content]); const columns = useMemo(() => { if (!data || data.length === 0) return []; const firstRow = data[0]; if (!firstRow || typeof firstRow !== 'object') return []; return Object.keys(firstRow); }, [data]); if (!mounted) return null; if (!data || data.length === 0) return null; const rowKey = row => columns.map(c => row[c] || '').join('|'); return
| {col.replaceAll('_', ' ')} | )}
|---|
| {processBadges(row[col])} | )}
This combination returns only projects that use npm packages, are from GitHub, have more than one package, and have a reachability analysis status of at least 90%.
## Filter implementation techniques
You can use the following filter types to manage your projects effectively.
* [Preset filters](#preset-filters): Use predefined UI-based filters to quickly segment projects by common attributes.
* [Filter projects using API](#filter-projects-using-api): Use advanced syntax for complex queries and logical combinations.
### Preset filters
The following examples demonstrate how to apply preset filters for common project scenarios.
#### Filter projects by custom tags
Use custom tags to filter projects based on environment or predefined labels assigned during project initialization or scan configuration.
For example, to view only projects related to SAST, use the `Custom Tags contains: sast` filter.
#### Filter projects by findings severity
Prioritize remediation efforts by filtering projects based on the severity of security findings. You can select from **Critical (C)**, **High (H)**, **Medium (M)**, or **Low (L)** severity filters to target different priority levels.
For example, to identify projects with critical findings, select the **C** filter.
#### Filter projects by package ecosystem
Use package ecosystem filters to segment projects by language or package manager. Apply targeted policies, such as stricter vulnerability thresholds for JavaScript or license compliance checks for Java.
For example, to focus on PHP projects for a security assessment, use the `Package Ecosystems contains: Packagist` filter.
#### Filter projects by source platform
Use platform source filters to segment projects by their source platform and correlate findings with platform-native security tools like GitHub's Dependabot alerts or GitLab's vulnerability scanning.
For example, to identify projects analyzed from GitLab, use the `Platform Source in: GitLab` filter.
#### Filter projects by dependency resolution quality
Use dependency resolution status to identify projects with resolution issues that impact security analysis accuracy. You can filter by a single value or a range of percentages.
For example, to identify projects with poor dependency resolution, use the **Range** filter to find projects with `Dependency Resolution Status greater than 0% and less than 50%`.
#### Filter projects by scan timestamp
Use last scanned filters to identify projects with stale security data that require fresh scans for current security posture. You can select from predefined time ranges or use the calendar to select a specific date.
For example, to identify projects scanned within the last 24 hours, use the `Last Scanned: Last Day` filter.
#### Filter projects by complexity
Identify projects based on their size and complexity, which may require different levels of security attention and resources.
For example, to focus on large projects with extensive dependency trees, use the `Package Count: greater than 100` filter.
#### Filter projects by reachability analysis status
Use reachability analysis status to identify projects based on the success rate of call graph generation and reachability analysis. You can filter by a single value or a range of percentages.
For example, to identify projects with successful reachability analysis, use the `Reachability Analysis Status greater than or equal to: 90%` filter.
### Filter projects using API
For complex queries, use the advanced filter syntax to combine multiple attributes and apply logical operators. Use the [Project filter builder](#interactive-filter-builder) to assemble conditions interactively.
The following table lists the available attributes for project filters.