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 🙏

© 2024 – Pkg Stats / Ryan Hefner

auditing-service

v1.0.1

Published

An audit logging service for MongoDB crud operations

Downloads

2

Readme

auditing-service

Description

This is an audit logging package which logs all the crud operations performed in a database collection in MongoDB. Essentially, all the crud operations performed are stored in a separate collection consisting of the following fields:

dbName
ipAddress
operation
documentID
dataBefore
dataAfter
outcome
time

🔥 Getting Started

  1. Install this package using "npm install auditing-service".
  2. Import the package in your code.
const auditingService = require("auditing-service");
  1. Initialize the package by invoking "initAudit" function. By default, a collection named "audit_trails" will be created in a database named "auditDB".
auditingService.initAudit(YOUR_MONGO_URI);
// Eg - auditingService.initAudit(mongodb+srv://username:password@something_here.mongodb.net/);

// OR

auditingService.initAudit(YOUR_MONGO_URI, YOUR_DB_NAME, YOUR_COLLECTION_NAME);
// Eg - auditingService.initAudit(mongodb+srv://username:password@something_here.mongodb.net/, "abcDB", "myAuditTrails");

⚡ Usage

(a) CREATE

Success Scenario

// Function prototype
auditingService.createAudit(oldData, newData, outcome);

// Example
auditingService.createAudit(
  null,
  {
    name: "John",
    age: 21,
    school: "ABC",
  },
  "success"
);

For a success scenario, before create operation is performed, oldData is null. If the operation is successful, the newData should not be null and outcome is "success".

Failure Scenario

// Function prototype
auditingService.createAudit(oldData, newData, outcome);

// Example
auditingService.createAudit(null, null, "failure");

For a failure scenario, before create operation is performed, oldData is null. If the operation fails, the newData should be null and outcome is "failure".

(b) READ

Success Scenario

// Function prototype
auditingService.reeadAudit(oldData, newData, outcome);

// Example
auditingService.readAudit(
  [
    {
      name: "John",
      age: 21,
      school: "ABC",
    },
    {
      name: "Bill",
      age: 31,
      school: "CDF",
    },
  ],
  {
    name: "John",
    age: 21,
    school: "ABC",
  },
  "success"
);

For a success scenario, before read operation is performed, oldData is not null. If the operation is successful, the newData should not be null as well and outcome is "success". The oldData/newData can be a single object or an array of objects.

Failure Scenario

// Function prototype
auditingService.readAudit(oldData, newData, outcome);

// Example
auditingService.readAudit(
  [
    {
      name: "John",
      age: 21,
      school: "ABC",
    },
    {
      name: "Bill",
      age: 31,
      school: "CDF",
    },
  ],
  null,
  "failure"
);

For a failure scenario, before read operation is performed, oldData is not null. If the operation fails, the newData should be null and outcome is "failure". The oldData can be a single object or an array of objects.

(c) UPDATE

Success Scenario

// Function prototype
auditingService.updateAudit(oldData, newData, outcome);

// Example
auditingService.updateAudit(
  {
    name: "John",
    age: 21,
    school: "ABC",
  },
  {
    name: "Bill",
    age: 31,
    school: "CDF",
  },
  "success"
);

For a success scenario, before update operation is performed, oldData is not null. If the operation succeeds, the newData should not be null as well and outcome is "success".

Failure Scenario

// Function prototype
auditingService.updateAudit(oldData, newData, outcome);

// Example
auditingService.updateAudit(
  {
    name: "John",
    age: 21,
    school: "ABC",
  },
  {
    name: "John",
    age: 21,
    school: "ABC",
  },
  "failure"
);

For a failure scenario, before update operation is performed, oldData is not null. If the operation succeeds, the newData should be equal to oldData and outcome is "failure".

(d) DELETE

Success Scenario

// Function prototype
auditingService.deleteAudit(oldData, newData, outcome);

// Example
auditingService.deleteAudit(
  {
    name: "John",
    age: 21,
    school: "ABC",
  },
  null,
  "success"
);

For a success scenario, before delete operation is performed, oldData is not null. If the operation succeeds, the newData should be null and outcome is "success".

Failure Scenario

// Function prototype
auditingService.deleteAudit(oldData, newData, outcome);

// Example
auditingService.deleteAudit(
  {
    name: "John",
    age: 21,
    school: "ABC",
  },
  {
    name: "John",
    age: 21,
    school: "ABC",
  },
  "failure"
);

For a failure scenario, before delete operation is performed, oldData is not null. If the operation fails, the newData should be equal to oldData and outcome is "failure".