npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

moc-oauth-client

v1.0.8

Published

OAuth client for Ministry of Commerce, Cambodia

Readme

moc-oauth-client

Official OAuth Client SDK for integrating applications with the Ministry of Commerce (MOC) Identity & OAuth Service.

This package provides a simple, type-safe way to:

  • Authorize OAuth clients
  • Validate JWT access tokens
  • Retrieve authenticated user information
  • Refresh access tokens

Built with TypeScript and designed for Node.js applications.


📦 Installation

npm install moc-oauth-client

⚙️ Environment Configuration

Create a .env file in your application:

touch .env

Add the following environment variables to your .env file:

BASE_URL=https://api-dev-dentity.moc.gov.kh
CLIENT_ID=your_client_id
CLIENT_SECRET=your_client_secret
REDIRECT_URI=https://example.com/callback

🚀 Quick Start

import { MOCOAuthClient } from "moc-oauth-client";

const oauth = new MOCOAuthClient();

🔐 Authorize Client

const result = await oauth.authorizeClient();

console.log(result);

✅ Success Response

{
  "data": {
    "redirectUri": "http://localhost:3000/login?loginToken=..."
  },
  "error": null
}

✅ Validate Access Token

const result = await oauth.validateToken(accessToken);

console.log(result);

✅ Success Response

{
  "data": {
    "isValid": true,
    "accessToken": "...",
    "refreshToken": "..."
  },
  "error": null
}

👤 Get Current User Retrieve authenticated user information.

const result = await oauth.getCurrentUser(accessToken);

console.log(result);

✅ Success Response

{
  "data": {
    "email": "[email protected]",
    "firstName": "Sok",
    "lastName": "Dara"
  },
  "error": null
}

🔄 Refresh Token Generate a new access token using refresh token.

const result = await oauth.refreshToken(refreshToken);

console.log(result);

✅ Success Response

{
  "data": {
    "accessToken": "...",
    "refreshToken": "..."
  },
  "error": null
}

❌ Error Handling

All API errors follow a standardized format:

{
  "error": {
    "code": "UNAUTHORIZED",
    "message": "Invalid token"
  }
}

Example handling:

try {
  await oauth.validateToken(token);
} catch (error) {
  console.error(error.error.message);
}

🏗 Requirements

  • Node.js >= 18
  • Valid MOC OAuth Client credentials

🔐 Security Notes

  • MOC OAuth Client credentials should be kept secret and not shared with any third parties.
  • Access tokens should be handled securely and not exposed to untrusted clients.
  • Never expose CLIENT_SECRET in frontend applications.
  • This SDK is intended for backend/server-side usage.