18 |
19 | 
6 | [](https://github.com/ellerbrock/open-source-badges/)
7 | [](https://github.com/prettier/prettier)
8 |
9 |
10 |
11 | NumValidate is a phone validation REST API powered by Google LibPhoneNumber, a phone number formatting and parsing library released by Google, originally developed for (and currently used in) Google's Android mobile phone operating system, which uses several rigorous rules for parsing, formatting, and validating phone numbers for all countries/regions of the world.
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 |
21 | numvalidate.com 22 |
23 | 24 | ## Disclaimer 25 | 26 | NumValidate is currently out of service becacuse in December 2017 Auth0 has stopped supporting the core API authorization mechanism used by the app (querying for users by `app_metadata`). 27 | 28 |
29 |
30 | From my understanding the Auth0 team is not planning to re-introduce this feature anymore.
31 |
32 | ## Overview
33 |
34 | In this repository you'll be able to find everything you'll need to setup your own NumValidate platform.
35 |
36 | Even if you're not interested in phone number validation, I suggest you to take a look around here, since **you can easily customize NumValidate to expose any kind of API you like**: the phone validation APIs consists in [> 200 line of codes](https://github.com/mmazzarolo/numvalidate/blob/master/server/routes/api.js), while the remaining code supports the authentication, authorization, plan subscription, plan payment and API tokens management.
37 |
38 | ### Features
39 | - Plain simple phone number validation rest API, powered by [Google LibPhoneNumber](https://github.com/googlei18n/libphonenumber) and [documented](https://github.com/mmazzarolo/numvalidate-docs) with [Slate](https://github.com/lord/slate)
40 | - Server-side rendered responsive React website/landing-page (~160kb GZipped)
41 | - Private API tokens generation and management for authenticated users through the Dashboard
42 | - Fully featured authentication for accessing the Dashboard: email + password, Github and Google login thanks to [Auth0](https://auth0.com/)
43 | - API requests with different rate limits for unauthenticated user, free user and pro user, updated in real time after a subscription change
44 | - Secure payment for paid subscriptions handled by [Stripe](https://stripe.com): change your payment method at any given time
45 | - API tokens cached with Redis for faster response time on consecutive requests
46 | - Production ready logging and error reporting using Winston, [Sentry](https://sentry.io) and [Papertrail](https://papertrailapp.com/)
47 |
48 | ### Stack
49 | - Node.js - (Web Server)
50 | - React - (Website and dashboard UI)
51 | - Next - (Routing, Server Side Rendering and code splitting)
52 | - Koa - (Web App Server)
53 | - Redis - (Caching)
54 | - Flow - (Static Types in the Dashboard)
55 | - ESLint - (JS Best Practices/Code Highlighting)
56 |
57 | ### External services and platforms
58 | - [Auth0](https://auth0.com/) - (Authentication and authorization)
59 | - [Stripe](https://stripe.com) - (Payment processing)
60 | - [Papertrail](https://papertrailapp.com/) - (Log management)
61 | - [Sentry](https://sentry.io) - (Error tracking and reporting)
62 |
63 | ## Architecture
64 |
65 | ### The Client
66 | The client is a React application that exposes the **Home page** and the **Dashboard**: both pages are rendered server-side thanks to Next.
67 | To take advantage of Next server-side rendering, the app follows the convention of grouping the main routes under the `/pages` directory and putting all the static assets under `statics`.
68 |
69 | The app itself is not complex at all: the *Home page* is just a simple page that emphasizes the product features, while the *Dashboard* (available after a successfull signup) is used for generating API tokens and updating the user subscription plan.
70 |
71 | I tried to mimic the structure promoted by `create-react-app` as much as possible (since I love it for smaller sites), so I use plain CSS to style the components (with a touch of CSS just for supporting CSS Custom Variables for color names) and I don't use bleeding edge stuff like decorators et similia.
72 | For the same reason, you won't find any state management library here, since `setState` has proven to be more than than enough for this project.
73 |
74 | ```javascript
75 | client
76 | ├── components // The building blocks of the UI
77 | │ ├── Button.css
78 | │ ├── Button.js
79 | │ ├── DashboardCreditCard.css
80 | │ ├── DashboardCreditCard.js
81 | │ └── ...
82 | │
83 | ├── config
84 | │ ├── keys.js // Constants used across the app (mostly are env vars)
85 | │ └── strings.js // Almost every string used in the Dashboard
86 | │
87 | ├── pages // The actual pages (aka containers) server by Next
88 | │ ├── Dashboard.css
89 | │ ├── Dashboard.js
90 | │ ├── Home.css
91 | │ └── Home.js
92 | │
93 | ├── services
94 | │ ├── analytics.js // Simple wrapper over Google Analytics
95 | │ ├── auth.js // Auth0 APIs
96 | │ └── backend.js // Backend (server) APIs
97 | │
98 | ├── static // Static assets (favicons, images, robots.txt)
99 | │
100 | ├── utils // Common utils used in all the app
101 | │
102 | ├── colors.css // CSS colors variables
103 | │
104 | ├── globals.css // Global styles
105 | │
106 | ├── next.config // Babel config injected into Next
107 | │
108 | ├── postcss.config // PostCSS config injected into Next
109 | │
110 | └── types.js // Flowtype type definitions
111 | ```
112 |
113 | ### The Server
114 | The server is a Node application powered by Koa, responsible of handling all the API requests and rendering the website/dashboard.
115 | There is no database here: all the users info like the API tokens and the Stripe customer ID are stored in Auth0 in the user `appMetadata`. The endpoints defined in `routes/user.js` handles all the requests made by the Dashboard to manage the user info.
116 | To fetch and update the users info from Auth0 and validate the user JWT I use an [Auth0 API](https://auth0.com/docs/api/info) (defined in `services/auth0.js`) with granted permissions to many [Auth0 management API endpoints](https://auth0.com/docs/api/management/v2).
117 | The requests to the `/api` endpoints are rate limited by IP (for unauthenticated users) and by API token (for authenticated users).
118 |
119 | The most interesting part of the server is probably the API token rate limiting and caching, which grants a fast response time on consecutive requests. The flow is the following:
120 | - An authenticated user makes a request to an `/api` endpoint with an `x-api-token` header.
121 | - The API token is validated in `middlewares/checkApiToken.js`:
122 | - If the API token is not cached in Redis then the server searches for an user with that API token in Auth0 to check for its validity (and cache it)
123 | - If the API token is already cached in Redis, the Auth0 search is skipped
124 | - The API token user's daily usage limit is checked in `middlewares/checkMaxRequests.js`:
125 | - If the daily usage limit of the user is not cached in Redis then the server searches for it (and cache it) by fetching the user subscription plan on Stripe
126 | - If the daily usage limit of the user is cached in Redis, the Stripe fetch is skipped
127 | - If the user reached its daily API requests limit then the server doesn't finalize the call to the `/api` endpoint and returns a `429` status code instead (`middlewares/rateLimited.js`).
128 |
129 | The Redis cache expires after the milliseconds defined in the `REDIS_CACHE_EXPIRY_IN_MS` environment variable and after an user subscription plan change.
130 |
131 | ```javascript
132 | server
133 | ├── config
134 | │ ├── keys.js // Constants used across the app (mostly are env vars)
135 | │ └── strings.js // Almost every string used in the Dashboard
136 | │
137 | ├── middlewares
138 | │ ├── allowCrossDomain.js // CORS setup
139 | │ ├── auth0TokenGenerator.js // Daily Auth0 Management API token generator
140 | │ ├── checkApiToken.js // Validates the request API token
141 | │ ├── checkAuthToken.js // Validates the request Auth0 JWT
142 | │ ├── checkMaxRequests.js // Checks the max requests limit of the user
143 | │ ├── checkStripeCustomer.js // Verifies that the user initialized in Stripe
144 | │ ├── errorHandler.js // Returns a clean response error
145 | │ ├── fetchUserFromAuth0.js // Given the Auth0 JWT gets the user from Auth0
146 | │ ├── getIpAddress.js // Gets the request IP address
147 | │ ├── rateLimiter.js // Blocks the request on max requests limit reached
148 | │ └── requestLogger.js // Logs the request on console/Papertrail/Sentry
149 | │
150 | ├── routes
151 | │ ├── api.js // Phone validation endpoints
152 | │ └── user.js // Dashboard endpoints
153 | │
154 | ├── services
155 | │ ├── auth0.js // Auth0 APIs wrapper
156 | │ ├── redis.js // Redis queries
157 | │ ├── sentry.js // Sentry APIs wrapper
158 | │ └── stripe.js // Stripe APIs wrapper
159 | │
160 | ├── static
161 | │ └── countries.json // Phone validation supported countries
162 | │
163 | ├── utils
164 | │ ├── common.js // Common utils used in all the app
165 | │ └── logger.js // Winston logger setup
166 | │
167 | ├── utils // Common utils used in all the app
168 | │
169 | ├── app.js // App setup
170 | │
171 | └── index.j // App entry point
172 | ```
173 |
174 | ## How To Start The Application
175 |
176 | ### Auth0 Setup
177 | To run this project you'll need an [Auth0](https://auth0.com/) account.
178 | Since this is a complex process, I'll detail it by using the naming convention I followed with NumValidate, by supposing that your app name is **"SuperApp"**
179 |
180 | Please make sure all the items in the following checklist are marked before running this project in development:
181 |
182 | - [ ] Create an account on [Auth0](https://auth0.com/) and head to the Auth0 [dashboard](https://manage.auth0.com/)
183 | - [ ] Create a new tenant (which basically is a sub-account) that you'll use for development (by clicking on your icon in the top right corner and selecting **Create tenant**) and name it **"superapp-dev"**
184 | - [ ] Create a new Single Page Application Client named **"SuperApp"**: it will be the used to signup/login users in Auth0
185 | - [ ] In the created client detail, add to the **Allowed Callback URLs** the URL you'll redirect the user after a succesfull login
186 | - [ ] Create a new API named **"SuperApp"**: it will be used to authenticate and authorize the Auth0 user to your server (by checking their JWT)
187 | - [ ] Create a new client named **"SuperApp Management API Client"**: it will be used for calling the Auth0 Management APIs for fetching and updating user informations
188 | - [ ] In Auth0 Management API details and in **Non Interactive Clients** enable your **Auths Management API client**
189 | - [ ] Super boring stuff ahead: since some essential permissions are not enabled by default on the **SuperApp** client, you'll need to [add them manually by making an API call to the Auth0 Management API](https://community.auth0.com/questions/3944/error-grant-type-password-not-allowed-for-the-clie)
190 |
191 |
192 | If you're ready for production, you'll need to replicate all the above stuff in a new tenant (named **superapp**) and also check the following:
193 |
194 | - [ ] If you use any social integration (Google, Facebook, etc...) you'll need to provide your own API token/secrets for that integration
195 | - [ ] Setup your own email service (Amazon Ses, Mandrill, etc...) for sending the Auth0 emails
196 | - [ ] Customize the email templates to better suit your needs
197 |
198 | I also suggest adding a custom rule for locking the user out of your app until it has not verified its email (it will still be able to access the app for the first day post-signup):
199 | ```javascript
200 | function (user, context, callback) {
201 | var oneDayPostSignup = new Date(user.created_at).getTime() + (24 * 60 * 60 * 1000);
202 | if (!user.email_verified && new Date().getTime() > oneDayPostSignup) {
203 | return callback(new UnauthorizedError('Please verify your email before logging in.'));
204 | } else {
205 | return callback(null, user, context);
206 | }
207 | }
208 | ```
209 |
210 | ### Redis Setup
211 | To run this project you'll need a running Redis instance.
212 |
213 | ### Stripe Setup
214 | To run this project you'll need a [Stripe](https://stripe.com) account.
215 |
216 | Please make sure all the items in the following checklist are marked before running this project in development:
217 |
218 | - [ ] Create an account on [Stripe](https://stripe.com) and head to the Stripe [dashboard](https://dashboard.stripe.com/dashboard)
219 | - [ ] Switch to the **test mode** by toggling the **View test data** button in the left sidebar
220 | - [ ] Subscription -> Plans -> Create a new plan with a price of 0.00€/$: it will be your app free plan
221 | - [ ] Subscription -> Plans -> Create a new plan with a price you like: it will be your app paid plan
222 |
223 | If you're ready for production, you'll need to create the above subscription outside of the **test mode** too, and verify your business settings.
224 |
225 | ### Setup
226 |
227 | Run the app in dev mode (including *hot module reloading*) with:
228 |
229 | ```bash
230 | npm install
231 | npm run start-dev
232 | ```
233 |
234 | Or, if you prefer using yarn, run the app with:
235 |
236 | ```bash
237 | yarn
238 | yarn start-dev
239 | ```
240 |
241 | To run in production mode:
242 |
243 | `npm run build && npm start`
244 |
245 | Or, with yarn:
246 |
247 | `yarn build && yarn start`
248 |
249 | ### Setup with Docker Compose
250 |
251 | This project supports [docker-compose](https://docs.docker.com/compose/).
252 | To run it, you must first:
253 | - rename [.env.client.example](https://github.com/mmazzarolo/numvalidate/blob/master/client/.env.client.example) to .env.client
254 | - rename [.env.server.example](https://github.com/mmazzarolo/numvalidate/blob/master/server/.env.server.example) to .env.server
255 | - run `docker-compose up -d` from the root folder of this repo
256 |
257 | If you want to check the output of a certain container, just run `docker-compose logs $CONTAINER_NAME`.
258 | `$CONTAINER_NAME` may be one of the following:
259 | - `redis`
260 | - `web`
261 |
262 | For additional infos, please check out [docker-compose.yml](https://github.com/mmazzarolo/numvalidate/blob/master/docker-compose.yml).
263 |
264 | ### Configuration
265 |
266 | This project makes an heavy use of environment variables for its configuration, so, if you want to run the project locally, you are adviced to include a `.env.server` and a `env.client` file in your project root (I use two dotenv files instead of one to keep the things clearer while developing).
267 |
268 | Client environment variables: (check [.env.client.example](https://github.com/mmazzarolo/numvalidate/blob/master/client/.env.client.example))
269 |
270 | | Environment Variable | Default | Description |
271 | | ------------- | ------------- | ------------- |
272 | | `REACT_APP_AUTH0_AUDIENCE` | *REQUIRED* | Auth0 audience |
273 | | `REACT_APP_AUTH0_CLIENT_ID` | *REQUIRED* | Auth0 ClientID |
274 | | `REACT_APP_AUTH0_DOMAIN` | *REQUIRED* | Auth0 domain |
275 | | `REACT_APP_RATE_LIMIT_FOR_UNAUTHENTICATED_REQUESTS` | 100 | Rate limit for unauthenticated users |
276 | | `REACT_APP_RATE_LIMIT_FOR_FREE_USER_REQUESTS` | 1000 | Rate limit for free users |
277 | | `REACT_APP_RATE_LIMIT_FOR_PRO_USER_REQUESTS` | 100000 | Rate limit for pro users |
278 | | `REACT_APP_STRIPE_FREE_PLAN_ID` | *REQUIRED* | Free plan ID in Stripe |
279 | | `REACT_APP_STRIPE_PRO_PLAN_ID` | *REQUIRED* | Pro plan ID in Stripe |
280 | | `REACT_APP_STRIPE_PRO_PLAN_AMOUNT` | 399 | The pro plan subscription amount in Stripe |
281 | | `REACT_APP_STRIPE_PUBLIC_KEY` | *REQUIRED* | Stripe API public key |
282 | | `REACT_APP_MAX_API_TOKENS_PER_USER` | 5 | The maximum number of API tokens per user |
283 | | `REACT_APP_GOOGLE_SITE_VERIFICATION` | OPTIONAL | The Google Search Console verification key |
284 |
285 | Server environment variables: (check [.env.server.example](https://github.com/mmazzarolo/numvalidate/blob/master/server/.env.server.example))
286 |
287 | | Environment Variable | Default | Description |
288 | | ------------- | ------------- | ------------- |
289 | | `PORT` | 1337| The port where the server will run |
290 | | `AUTH0_AUDIENCE` | *REQUIRED* | Auth0 audience |
291 | | `AUTH0_DOMAIN` | *REQUIRED* | Auth0 audience |
292 | | `AUTH0_ISSUER` | *REQUIRED* | Auth0 audience |
293 | | `AUTH0_JWKS_URI` | *REQUIRED* | Auth0 audience |
294 | | `AUTH0_MANAGEMENT_API_AUDIENCE` | *REQUIRED* | Auth0 audience |
295 | | `AUTH0_MANAGEMENT_API_CLIENT_ID` | *REQUIRED* | Auth0 audience |
296 | | `AUTH0_MANAGEMENT_API_CLIENT_SECRET` | *REQUIRED* | Auth0 audience |
297 | | `EXECUTION_ENV` | development | Used mainly for logging infos |
298 | | `RATE_LIMIT_FOR_UNAUTHENTICATED_REQUESTS` | 100 | Rate limit for unauthenticated users |
299 | | `RATE_LIMIT_FOR_FREE_USER_REQUESTS` | 1000 | Rate limit for free users |
300 | | `RATE_LIMIT_FOR_PRO_USER_REQUESTS` | 100000 | Rate limit for pro users |
301 | | `REDIS_URL` | *REQUIRED* | Redis URL |
302 | | `REDIS_CACHE_EXPIRY_IN_MS` | ms('1d') | Expiration of Redis cache in milliseconds |
303 | | `STRIPE_FREE_PLAN_ID` | *REQUIRED* | Free plan ID in Stripe |
304 | | `STRIPE_PRO_PLAN_ID` | *REQUIRED* | Pro plan ID in Stripe |
305 | | `STRIPE_PUBLIC_KEY` | *REQUIRED* | Stripe API public key |
306 | | `STRIPE_SECRET_KEY` | *REQUIRED* | Stripe API secret key |
307 | | `PAPERTRAIL_HOST` | *OPTIONAL* | Papertrail URL |
308 | | `PAPERTRAIL_PORT` | *OPTIONAL* | Papertrail port |
309 | | `SENTRY_DSN` | *OPTIONAL* | Sentry DSN |
310 |
311 | ## External Related Issues And Pull Requests
312 | - zeit/next.js - [Added side note about enabling gzip on Koa](https://github.com/zeit/next.js/pull/2867)
313 | - auth0/auth0.js - [Nonce does not match](https://github.com/auth0/auth0.js/issues/365)
314 | - auth0/auth0.js - [Auth0 API it not instantly synced to Auth0 data](https://github.com/auth0/auth0.js/issues/515)
315 | - auth0/node-auth0 - [Recommended way to re-inject renewed token for Management API in a long-running script?](https://github.com/auth0/node-auth0/issues/164)
316 |
317 |
318 | ## Contributing
319 | Pull requests are welcome. File an issue for ideas, conversation or feedback.
320 |
321 |
--------------------------------------------------------------------------------
/client/colors.css:
--------------------------------------------------------------------------------
1 | :root {
2 | --color-primary: #fff;
3 | --color-accent: #fff;
4 | --color-background: #21272f;
5 | --color-error: #d64242;
6 | --color-text-1: #fff;
7 | --color-text-2: rgba(255, 255, 255, 0.5);
8 | --color-grey-dark: rgba(255, 255, 255, 0.1);
9 | --color-grey-light: rgba(255, 255, 255, 0.5);
10 | --color-grey-lighter: rgba(255, 255, 255, 0.6);
11 | --color-grey-lightest: rgba(255, 255, 255, 0.8);
12 | }
--------------------------------------------------------------------------------
/client/components/Button.css:
--------------------------------------------------------------------------------
1 | @import '../colors';
2 |
3 | .Button {
4 | background: transparent;
5 | padding: 8px;
6 | text-transform: uppercase;
7 | text-align: center;
8 | border-radius: 3px;
9 | cursor: pointer;
10 | font-size: 14px;
11 | font-weight: 500;
12 | min-width: 100px;
13 | transition: all 0.25s ease-in-out;
14 | }
15 |
16 | .Button:hover:enabled {
17 | color: var(--color-background);
18 | background: var(--color-primary);
19 | }
20 |
21 | .Button:disabled {
22 | cursor: initial;
23 | color: var(--color-grey-dark);
24 | border: 2px solid var(--color-grey-dark);
25 | }
26 |
27 | .Button-default {
28 | color: var(--color-grey-lightest);
29 | border: 2px solid var(--color-grey-lightest);
30 | }
31 |
32 | .Button-info {
33 | padding: 6px;
34 | font-size: 12px;
35 | color: var(--color-grey-lightest);
36 | border: 2px solid var(--color-grey-lightest);
37 | }
38 |
39 | .Button-medium {
40 | }
41 |
42 | .Button-big {
43 | font-weight: bold;
44 | padding: 14px 42px;
45 | }
46 |
47 | .Button-big:hover:enabled,
48 | .Button-big:focus {
49 | transform: scale(1.05);
50 | }
51 |
52 | .Button-flat {
53 | font-weight: bold;
54 | border: none;
55 | }
56 |
57 | .Button-warn {
58 | color: #fdbc72;
59 | }
60 |
61 | .Button-danger {
62 | color: #c23d4b;
63 | }
64 |
65 | .Button-fill {
66 | width: 100%;
67 | }
--------------------------------------------------------------------------------
/client/components/Button.js:
--------------------------------------------------------------------------------
1 | /* @flow */
2 | import React, { Component } from 'react';
3 | import style from './Button.css';
4 |
5 | type Props = {
6 | type?: 'default' | 'info' | 'warn' | 'danger',
7 | size?: 'medium' | 'big',
8 | fill?: boolean,
9 | flat?: boolean,
10 | children?: any,
11 | };
12 |
13 | class Button extends Component{subtitle}
41 |77 | 78 | {strings.PAYMENT_INFO_FREE_PLAN_AMOUNT} 79 | 80 | {' - '} 81 | 82 | {strings.PAYMENT_INFO_FREE_PLAN_DESCRIPTION} 83 | 84 |
85 |88 | {strings.SUBSCRIPTION_CURRENT_PLAN} 89 |
90 | )} 91 | {userSubscription.planId !== keys.STRIPE_FREE_PLAN_ID && ( 92 | 99 | )} 100 |104 | 105 | {strings.PAYMENT_INFO_PRO_PLAN_AMOUNT} 106 | 107 | {' - '} 108 | 109 | {strings.PAYMENT_INFO_PRO_PLAN_DESCRIPTION} 110 | 111 |
112 |115 | {strings.SUBSCRIPTION_CURRENT_PLAN} 116 |
117 | )} 118 | {userSubscription.planId !== keys.STRIPE_PRO_PLAN_ID && ( 119 | 126 | )} 127 |{text}
23 |![{"Delete"}]({"/static/ic_delete_white_24px.svg"})
157 | {'Back'}
24 |{message}
21 | 24 |{label}
} 17 | 18 |{error}
19 |{this.state.initializationError}
168 | 171 |78 | NumValidate is an open source REST API that provides a simple yet effective way to 79 | validate and format a phone number. 80 |
81 |136 | If your project is open source or you just need an higher rate limit feel free to{' '} 137 | 141 | contact me 142 | 143 | . 144 |
145 |154 | NumValidates is powered by{' '} 155 | 156 | Google LibPhoneNumber 157 | , a phone number formatting and parsing library released by Google, originally 158 | developed for (and currently used in) Google's Android mobile phone operating system, 159 | which uses several rigorous rules for parsing, formatting, and validating phone 160 | numbers for all countries/regions of the world. 161 |
162 |
166 | Validating a phone number allows you to keep your user database clean and fight frauds
167 | by validating phone numbers at the point of entry into your system.
NumValidate
168 | also allows you to format a phone number in the{' '}
169 |
170 | E164 format
171 | , which is the standard that you should use for safely storing you phone numbers.
172 |
177 | Simply put: the rate limit ensures an high quality of service for all API consumers.
{' '}
178 | To enjoy the default rate limit of {keys.RATE_LIMIT_FOR_FREE_USER_REQUESTS} requests
179 | per day, you'll need to sign-up for a free account and then head to your dashboard to
180 | generate an API keys.
181 |
186 | The paid plan{' '}
187 |
188 | should
189 | {' '}
190 | be the main way to pay up the infrastructure.
However, this is an open source
191 | project: You can find all its code on{' '}
192 |
193 | Github
194 | , and if you think that the proposed price for the pro plan is too high you're
195 | free to install it in your own server.
196 | Payments can be made via Credit Card (Visa, MasterCard, Discover, Diner's Club) and
197 | are secured by{' '}
198 |
199 | Stripe
200 | .
You can change your payment method at any given time in the Payment section
201 | of your Account Dashboard.
202 |
207 | Of course!
208 | NumValidate was born in the summer 2017 from a meeting between the holiday boredom and
209 | the desire to test myself in building a "simple API gateway".
You can see by
210 | yourself in the Github repository that only a small portion of the code handles the
211 | phone number validation, while the biggest part of the project just supports the
212 | authentication, caching and API token management.
213 |
218 | I'm putting this in the FAQ even if we all know this is not a frequent question by any
219 | means シ.
If you're liking NumValidate, the best way to support the project is by
220 | contributing to it on Github: Pull requests with new features/fixes and discussions
221 | are warmly welcomed.
222 |
230 | Made with ♥ by{' '} 231 | 232 | Mazzarolo Matteo 233 | 234 |
235 |