Skip to content
1146345502

1146345502/aural-oss

Live in production

Self-hostable AI interviews over voice, chat, and video with adaptive follow-ups and structured scoring.

Open-source AI interview platform for voice, chat & video

197 53 since joining 69TypeScriptPush 8d agoListed 1mo agoMIT

aural-ai.com

aiai-interviewhiringinterview-platformnextjsopen-sourceopenaireact
  • TypeScript97.9%
  • PLpgSQL1.3%
  • HTML0.6%
  • CSS0.2%
  • JavaScript0.0%
View on GitHub

Report a problem

1 Review

Aural is a large and impressive open-source interview platform. It covers voice, chat, video, live coding, whiteboards, interview generation, candidate invitations, reports, practice sessions, organizations, role-based access, and a developer API. The repository backs those claims with extensive product screenshots, user documentation, an English and Chinese README, contribution files, a security policy, CI, releases, and a substantial test suite. Tests cover authentication, API keys, rate limits, account deletion, session handling, scoring, audio, voice reconnection, URL fetching, PDF output, AI generation, and security regressions. Recent CI and CodeQL checks are passing, although some automated dependency update attempts have failed and should continue to be monitored.

Because Aural is used for interviews and candidate assessment, its most important improvements concern fairness, privacy, and human oversight. AI scores and reports can affect real opportunities. The documentation should clearly explain that model output is assistance rather than objective proof, describe known limits and bias risks, and encourage trained human review before decisions are made. Score explanations, confidence indicators, appeal paths, and regular fairness testing across languages, accents, disabilities, and connection quality would help users apply the tool responsibly.

The anti-cheating features also need careful wording. Tab changes, paste events, or multiple displays can have innocent causes and should be recorded as signals, not treated as proof of misconduct. Candidates should be told what is monitored before a session starts. Data retention controls should cover resumes, recordings, transcripts, video, generated reports, and model-provider logs. Administrators need clear deletion settings, consent records, regional storage details, and instructions for handling access requests.

For contributors, the README is rich but long. A shorter self-hosting checklist with required services, expected costs, test data, and a verified local demo path would reduce setup mistakes. Aural already demonstrates strong product depth and testing. Clearer safeguards around scoring, monitoring, consent, and retention would make the platform more trustworthy in a high-impact setting.