open-index/open-npm huggingface dataset:
npm package: @reyesossorio/logmate
Description: Simple logger
Author: reyesossorio
Latest version: 1.0.0

# LogMate

A simple, lightweight Node.js logger with basic log levels and timestamps.


## Features

- Five log levels: `trace`,`debug`,`info`, `warn`, `error`
- Timestamps included in each log
- Logs levels with colors
- Minimal, zero-dependency design
- Easy to use

## Installation

```bash
npm install logmate
```

## Usage

```javascript
const logger = require('logMate');

//trace log
logger.trace("This is a trace message");

//debug log
logger.debug("This is a debug message");

// Info log
logger.info("This is an info message");

// Warning log
logger.warn("This is a warning");

// Error log
logger.error("Something went wrong");

// Change logger level
logger.setLevel("warn");

```

## Output Example

```
[TRACE] [2025-10-25 14:31:9:01]  This is a trace message
[DEBUG] [2025-10-25 14:31:12:30] This is a debug message
[INFO]  [2025-10-25 14:32:10:01] This is an info message
[WARN]  [2025-10-25 14:32:12:03] This is a warning
[ERROR] [2025-10-25 14:32:15:06] Something went wrong
```
npm package: @reyhan6610/libsignal
Description: Open Whisper Systems' libsignal for Node.js
Author: REYHAN6610
Latest version: 0.0.1

<div align="center">
  <p><em>Signal protocol implementation for Node.js based on Javascript ✨</em></p>

  <img src="https://qu.ax/SrVPQ.jpeg" width="300" alt="Elaina Bail Banner" />

---
`If a bug or error occurs, contact me on WhatsApp. `
 
 [![WhatsApp](https://img.shields.io/badge/Chat%20on-WhatsApp-25D366?logo=whatsapp&logoColor=white)](https://wa.me/6285282530851)
 

Overview
--------
A ratcheting forward secrecy protocol that works in synchronous and
asynchronous messaging environments.

This Libsignal project was developed by myself `REYHAN6610`
Libsignal Fork Results - `@baileys`

PreKeys
--------
This protocol uses a concept called 'PreKeys'. A PreKey is an ECPublicKey and
an associated unique ID which are stored together by a server. PreKeys can also
be signed.

At install time, clients generate a single signed PreKey, as well as a large
list of unsigned PreKeys, and transmit all of them to the server.


Sessions
--------
Signal Protocol is session-oriented. Clients establish a "session," which is
then used for all subsequent encrypt/decrypt operations. There is no need to
ever tear down a session once one has been established.

Sessions are established in one of two ways:

1. PreKeyBundles. A client that wishes to send a message to a recipient can
   establish a session by retrieving a PreKeyBundle for that recipient from the
   server.
2. PreKeySignalMessages. A client can receive a PreKeySignalMessage from a
   recipient and use it to establish a session.


State
--------
An established session encapsulates a lot of state between two clients. That
state is maintained in durable records which need to be kept for the life of
the session.

State is kept in the following places:

* Identity State. Clients will need to maintain the state of their own identity
  key pair, as well as identity keys received from other clients.
* PreKey State. Clients will need to maintain the state of their generated
  PreKeys.
* Signed PreKey States. Clients will need to maintain the state of their signed
  PreKeys.
* Session State. Clients will need to maintain the state of the sessions they
  have established.


License
--------
Licensed under the GPLv3: https://opensource.org/license/mit

* Copyright 2015-2016 Open Whisper Systems
* Copyright 2017-2018 Forsta Inc
npm package: @reykjavik/hanna-react
Description: The official React components for Hanna – Reykjavík's design-system
Author: Reykjavík
Latest version: 0.10.171

# @reykjavik/hanna-react <!-- omit from toc -->

The official React components for Hanna – Reykjavík's design-system

```
yarn add @reykjavik/hanna-react
```

Components aim to be framework-agnostic and avoid unneccessary local state –
always preferring "controlled" use.

(See [README-conventions.md](./README-conventions.md) for more info.)

## Versioning

This module always targets the most recent version of the Hanna markup
patterns (currently **Hanna 0.8**).

<!--
	**NOTE:**
	If need arises we may decide to branch the repo and publish separate
	legacy modules (i.e. `@reykjavik/hanna_1-react`) that provide active
	long-term-support for older major-versions of Hanna's markup patterns.
-->

The version number of the `@reykjavik/hanna-react` package reflects changes in
the React Component signatures, dependencies, etc. and may have major releases
at much higher rate than Hanna's markup patterns.

Note, however, that a major version update to the Hanna markup patterns
automatically triggers a major version bump in this package.

If you need a version of this package that "targets" an older Hanna markup
version, you'll find the appropriate package version in the
[change log](https://github.com/rvk-utd/hanna/blob/main/modules/hanna-react/CHANGELOG.md).

## CSS

Each component is paired with a CSS file that can be loaded via the Hanna CSS
server – <https://styles.reykjavik.is>

If your project uses `<Layout/>`, `<HeroBlock/>`, `<TextInput/>`,
`<Selectbox/>` and `<ButtonPrimary/>` you can load the required CSS by linking
to
<https://styles.reykjavik.is/bundle/v0.8?m=-basics,Layout,HeroBlock,TextInput,Selectbox,ButtonPrimary>

The preferred way to build the CSS URL is to use the helper `getCssBundleUrl`:

```js
import { getCssBundleUrl } from '@reykjavik/hanna-css';

const cssUrl = getCssBundleUrl([
  '-basics',
  'Layout',
  'HeroBlock',
  'TextInput',
  'Selectbox',
  'ButtonPrimary',
]);
```

**NOTE:** The `-basics` URL token adds basic CSS resets, `@font-face`
declarations global color-variables, etc.

For best result, try and make sure each web page has **only one `<link />`**
to the CSS server to avoid unpredictable styling behavior.

<!--
## Older versions

To view the documentation for older versions of Hanna, check out the
corresponding branches in the git repo.

-->

## Changelog

See
[CHANGELOG.md](https://github.com/rvk-utd/hanna/blob/main/modules/hanna-react/CHANGELOG.md)