/Good-Client-Bad-Client

Help us build a Credit Card Approval system - using Machine Learning!

Primary LanguageJupyter Notebook

Kicking Off Hacktoberfest with ACM-VIT!

Good Client, Bad Client

Help us build a Credit Card Approval System - Using Machine Learning!

made-by-acm license stars forks

Overview

The main motive of the project is to build a machine learning model to predict if an applicant is 'good' or 'bad' client, different from other tasks, the definition of 'good' or 'bad' is not given.

Credit score cards are a common risk control method in the financial industry. It uses personal information and data submitted by credit card applicants to predict the probability of future defaults and credit card borrowings. The bank is able to decide whether to issue a credit card to the applicant. Credit scores can objectively quantify the magnitude of risk.

In dataset,application_record.csv is the table/file that has information about all the customers regarding their socio-economic status and credit_record.csv is the file/table that has all the payment/default records for a given client.

Usage

Run the following command to install all the required packages for this project

pip install -r requirements.txt

Lets get started!


 git remote add
 git fetch 
 git merge

Dataset

Link to the data set is here.

Submitting a Pull Request

  • Fork the repository by clicking the fork button on top right corner of the page
  • Clone the target repository. To clone, click on the clone button and copy the https address. Then run
git clone [HTTPS-ADDRESS]
  • Go to the cloned directory by running
cd [NAME-OF-REPO]
  • Create a new branch. Use
 git checkout -b [YOUR-BRANCH-NAME]
  • Make your changes to the code. Add changes to your branch by using
git add .
  • Commit the chanes by executing
git commit -m "your msg"
  • Push to remote. To do this, run
git push origin [YOUR-BRANCH-NAME]
  • Create a pull request. Go to the target repository and click on the "Compare & pull request" button. Make sure your PR description mentions which issues you're solving.
  • Wait for your request to be accepted.

Guidelines for Pull Request

  • Avoid pull requests that :
    • are automated or scripted
    • that are plagarized from someone else's branch
  • Do not spam
  • Project maintainer's decision on validity of PR is final.

For additional guidelines, refer to participation rules

What counts as a PR?

Check out our issues and try to solve them !

Interacting with Issues

  • There are helper issues that detail all you have to do to complete the project.
    • Read the helper issues and work on the corresponding code in your fork of the repo.
    • If you have some doubt regarding the 'help' given, comment below the issue.
    • If you have some doubt not related to any 'helper issue/s' open, Open up a new issue, select doubt and fill in the template.
  • If you want to provide some extra help to fellow participants, open up a new helper issue. Don't include any solution/code!
  • Do not spam

Authors

Authors: Aryan Vats, Aditya Nalini, Varun Srinivasan