CodeScene does not provide a built-in feature to fully anonymize individual users across all analyses. However, there are several ways you can manage or partially anonymize users who are no longer active in your project:
1. Mark as Ex-Developer
By default, all contributors are considered active. If someone has left your company or project, you can mark them as an Ex-Developer in the Teams/Developers configuration settings - Developers section.
-
This change does not anonymize the user but ensures they are included in Knowledge Loss analyses rather than being considered an active contributor.
-
Their historical contributions will still be visible in technical analyses.
2. Exclude the Author from Analysis
If a user’s contributions are limited to actions like merging pull requests (e.g., system integrators or automation users), you can choose to exclude them from social analyses:
-
Enable the “Exclude author from all analyses” setting for that user.
-
Their activity will be ignored in social metrics (like team collaboration or knowledge sharing), but will still appear in technical metrics such as Hotspots and Code Churn.
3. Alias Mapping (Pseudo-Anonymization)
If you want to hide the user’s real identity, you can use Alias Mapping to rename them:
-
Navigate to the Alias Mapping section in your Teams/Developers configuration settings.
-
Map the original name/email to a generic alias (e.g.,
"former.dev@example.com" → "Former Developer"). -
After re-running the analysis, this alias will be used in all analysis results, effectively anonymizing the developer’s identity in the user interface and reports.
Note: This is not a security feature. The underlying Git history remains unchanged, and a technically skilled person could still trace the original author via commit metadata.
Summary
Goal vs Recommended Approach:
- Remove from social analysis: Exclude the author from the analysis
- Mark as no longer active: Set as Ex-Developer
- Mask name in results: Use Alias Mapping