🚀 Socket Launch Week Day 5:Introducing Repository Access Permissions and Custom Roles.Learn more
Sign In

@cityssm/unique-timed-entry-queue

Package Overview
Dependencies
Maintainers
1
Versions
6
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@cityssm/unique-timed-entry-queue - npm Package Compare versions

Comparing version
0.4.0
to
0.4.1
+12
-6
package.json
{
"name": "@cityssm/unique-timed-entry-queue",
"version": "0.4.0",
"version": "0.4.1",
"description": "A queue with delayed enqueue of unique entries, perfect for queuing update notifications.",

@@ -19,2 +19,3 @@ "keywords": [

"author": "The Corporation of the City of Sault Ste. Marie",
"sideEffects": false,
"type": "module",

@@ -25,2 +26,7 @@ "exports": {

},
"files": [
"debug.*",
"index.*",
"utilities.*"
],
"scripts": {

@@ -32,10 +38,10 @@ "coverage": "c8 --reporter=lcov --reporter=text --reporter=text-summary node --test",

"debug": "^4.4.3",
"exit-hook": "^5.0.1"
"exit-hook": "^5.1.0"
},
"devDependencies": {
"@types/debug": "^4.1.12",
"@types/node": "^25.0.10",
"eslint-config-cityssm": "^36.1.0",
"prettier-config-cityssm": "^1.0.0"
"@types/debug": "^4.1.13",
"@types/node": "^25.6.0",
"eslint-config-cityssm": "^39.1.0",
"prettier-config-cityssm": "^2.1.2"
}
}

@@ -1,2 +0,2 @@

# Unique, Timed-Entry Queue for Node
# Unique Timed-Entry Queue for Node

@@ -3,0 +3,0 @@ [![DeepSource](https://app.deepsource.com/gh/cityssm/node-unique-timed-entry-queue.svg/?label=active+issues&show_trend=true&token=7XhMG59eghaYWmwSFMmUt71O)](https://app.deepsource.com/gh/cityssm/node-unique-timed-entry-queue/)

@@ -1,2 +0,1 @@

// eslint-disable-next-line @eslint-community/eslint-comments/disable-enable-pair
/* eslint-disable sonarjs/pseudo-random */

@@ -3,0 +2,0 @@ /**

@@ -1,2 +0,1 @@

// eslint-disable-next-line @eslint-community/eslint-comments/disable-enable-pair
/* eslint-disable sonarjs/pseudo-random */

@@ -3,0 +2,0 @@

# Contributor Covenant Code of Conduct
## Our Pledge
We as members, contributors, and leaders pledge to make participation in our
community a harassment-free experience for everyone, regardless of age, body
size, visible or invisible disability, ethnicity, sex characteristics, gender
identity and expression, level of experience, education, socio-economic status,
nationality, personal appearance, race, caste, color, religion, or sexual
identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming,
diverse, inclusive, and healthy community.
## Our Standards
Examples of behavior that contributes to a positive environment for our
community include:
- Demonstrating empathy and kindness toward other people
- Being respectful of differing opinions, viewpoints, and experiences
- Giving and gracefully accepting constructive feedback
- Accepting responsibility and apologizing to those affected by our mistakes,
and learning from the experience
- Focusing on what is best not just for us as individuals, but for the overall
community
Examples of unacceptable behavior include:
- The use of sexualized language or imagery, and sexual attention or advances of
any kind
- Trolling, insulting or derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or email address,
without their explicit permission
- Other conduct which could reasonably be considered inappropriate in a
professional setting
## Enforcement Responsibilities
Community leaders are responsible for clarifying and enforcing our standards of
acceptable behavior and will take appropriate and fair corrective action in
response to any behavior that they deem inappropriate, threatening, offensive,
or harmful.
Community leaders have the right and responsibility to remove, edit, or reject
comments, commits, code, wiki edits, issues, and other contributions that are
not aligned to this Code of Conduct, and will communicate reasons for moderation
decisions when appropriate.
## Scope
This Code of Conduct applies within all community spaces, and also applies when
an individual is officially representing the community in public spaces.
Examples of representing our community include using an official e-mail address,
posting via an official social media account, or acting as an appointed
representative at an online or offline event.
## Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be
reported to the community leaders responsible for enforcement at
**<corporateapps@cityssm.on.ca>**.
All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the
reporter of any incident.
## Enforcement Guidelines
Community leaders will follow these Community Impact Guidelines in determining
the consequences for any action they deem in violation of this Code of Conduct:
### 1. Correction
**Community Impact**: Use of inappropriate language or other behavior deemed
unprofessional or unwelcome in the community.
**Consequence**: A private, written warning from community leaders, providing
clarity around the nature of the violation and an explanation of why the
behavior was inappropriate. A public apology may be requested.
### 2. Warning
**Community Impact**: A violation through a single incident or series of
actions.
**Consequence**: A warning with consequences for continued behavior. No
interaction with the people involved, including unsolicited interaction with
those enforcing the Code of Conduct, for a specified period of time. This
includes avoiding interactions in community spaces as well as external channels
like social media. Violating these terms may lead to a temporary or permanent
ban.
### 3. Temporary Ban
**Community Impact**: A serious violation of community standards, including
sustained inappropriate behavior.
**Consequence**: A temporary ban from any sort of interaction or public
communication with the community for a specified period of time. No public or
private interaction with the people involved, including unsolicited interaction
with those enforcing the Code of Conduct, is allowed during this period.
Violating these terms may lead to a permanent ban.
### 4. Permanent Ban
**Community Impact**: Demonstrating a pattern of violation of community
standards, including sustained inappropriate behavior, harassment of an
individual, or aggression toward or disparagement of classes of individuals.
**Consequence**: A permanent ban from any sort of public interaction within the
community.
## Attribution
This Code of Conduct is adapted from the [Contributor Covenant][homepage],
version 2.1, available at
[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
Community Impact Guidelines were inspired by
[Mozilla's code of conduct enforcement ladder][mozilla coc].
For answers to common questions about this code of conduct, see the FAQ at
[https://www.contributor-covenant.org/faq][faq]. Translations are available at
[https://www.contributor-covenant.org/translations][translations].
[homepage]: https://www.contributor-covenant.org
[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
[mozilla coc]: https://github.com/mozilla/diversity
[faq]: https://www.contributor-covenant.org/faq
[translations]: https://www.contributor-covenant.org/translations
# Thank you for your interest in making this project better
Together, we can build high quality software that meets the needs of municipalities,
while remaining open and budget conscious.
**Thank you for taking the time to read the contributing guidelines.**
## All contributions are welcome
Being a very small team, contributions are greatly appreciated. How can you contribute?
- **Promote this project!**
- Documentation and tutorials
- Submit bug reports (or fix them!)
- Request new features (or build them!)
## Please Read the Code of Conduct
The [Code of Conduct](CODE_OF_CONDUCT.md) document describes how we should act when working together.
Be nice! 🙂
## How to report a bug or suggest an enhancement
**If you find a security vulnerability, do NOT open an issue. Email
<corporateapps@cityssm.on.ca> instead.**
For all other bug reports, feature requests, or enhancements,
open an issue and use the closest template.
## Thanks Again
We are a very small team with big aspirations and limited resources.
Thank you for helping with this project in any way you can!
# Security Policy
**Thank you for your interest in keeping this project safe for everyone.**
## Supported Versions
Due to limited resources, only the latest version is supported only for security updates.
## Reporting a Vulnerability
To report a security vulnerability,
please email <corporateapps@cityssm.on.ca>.
Every attempt will be made to resolve confirmed vulnerabilities
in a timely manner.