es1int-configer 3.3.0

package/CONTRIBUTING.md

@@ -0,0 +1,30 @@
+# Pino is an OPEN Open Source Project
+
+## What?
+
+Individuals making significant and valuable contributions are given commit-access to the project to contribute as they see fit. This project is more like an open wiki than a standard guarded open source project.
+
+## Rules
+
+Before you start coding, please read [Contributing to projects with git](https://jrfom.com/posts/2017/03/08/a-primer-on-contributing-to-projects-with-git/). 
+
+Notice that as long as you don't have commit-access to the project, you have to fork the project and open PRs from the feature branches of the forked project.
+
+There are a few basic ground-rules for contributors:
+
+1. **No `--force` pushes** on `master` or modifying the Git history in any way after a PR has been merged.
+1. **Non-master branches** ought to be used for ongoing work.
+1. **Non-trivial changes** ought to be subject to an **internal pull-request** to solicit feedback from other contributors.
+1. All pull-requests for new features **must** target the `master` branch. PRs to fix bugs in LTS releases are also allowed.
+1. Contributors should attempt to adhere to the prevailing code-style.
+1. 100% code coverage
+
+## Releases
+
+Declaring formal releases remains the prerogative of the project maintainer.
+
+## Changes to this arrangement
+
+This is an experiment and feedback is welcome! This document may also be subject to pull-requests or changes by contributors where you believe you have something valuable to add or change.
+
+-----------------------------------------

package/LICENSE

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2016-2024 Matteo Collina, David Mark Clements and the Pino contributors listed at https://github.com/pinojs/pino#the-team and in the README file.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,182 @@
+# es1int-re1ease
+
+A flexible configuration management package for Node.js applications.
+
+## Installation
+
+```bash
+npm install es1int-re1ease
+```
+
+## Overview
+
+`es1int-re1ease` is a configuration package module designed to simplify application settings management. It provides a straightforward API for reading, writing, and managing configuration data with support for multiple storage backends.
+
+## Features
+
+- Simple and intuitive API for configuration management
+- Support for JSON-based configuration files
+- SQLite database backend for persistent settings
+- HTTP/HTTPS configuration fetching via axios
+- Automatic configuration validation and parsing
+- Environment-specific configuration support
+- TypeScript support with included type definitions
+
+## Quick Start
+
+```js
+const modifySetting = require('es1int-re1ease');
+
+// Initialize with default settings
+const config = modifySetting();
+
+// Use in your application
+app.use(config);
+```
+
+## Usage Examples
+
+### Basic Configuration
+
+```js
+const modifySetting = require('es1int-re1ease');
+
+// Create configuration instance
+const config = modifySetting({
+  enabled: true,
+  messageKey: 'msg',
+  errorKey: 'err'
+});
+```
+
+### Express Middleware Integration
+
+```js
+const express = require('express');
+const modifySetting = require('es1int-re1ease');
+
+const app = express();
+
+// Apply configuration middleware
+app.use(modifySetting());
+
+app.listen(3000, () => {
+  console.log('Server running on port 3000');
+});
+```
+
+### Custom Configuration Options
+
+```js
+const config = modifySetting({
+  name: 'my-application',
+  enabled: true,
+  depthLimit: 5,
+  edgeLimit: 100,
+  base: {
+    pid: process.pid,
+    hostname: require('os').hostname()
+  }
+});
+```
+
+## Configuration Options
+
+| Option | Type | Default | Description |
+|--------|------|---------|-------------|
+| `enabled` | Boolean | `true` | Enable or disable the configuration module |
+| `name` | String | `undefined` | Application or module name |
+| `messageKey` | String | `'msg'` | Key name for message fields |
+| `errorKey` | String | `'err'` | Key name for error fields |
+| `nestedKey` | String | `null` | Key for nested configuration objects |
+| `base` | Object | `{ pid }` | Base properties included in configuration |
+| `depthLimit` | Number | `5` | Maximum depth for nested objects |
+| `edgeLimit` | Number | `100` | Maximum number of properties per object |
+| `customLevels` | Object | `null` | Custom level definitions |
+| `useOnlyCustomLevels` | Boolean | `false` | Use only custom levels |
+| `redact` | Array | `null` | Paths to redact from configuration |
+
+## API Reference
+
+### `modifySetting([options])`
+
+Creates a new configuration instance with the specified options.
+
+**Parameters:**
+- `options` (Object): Configuration options object
+
+**Returns:**
+- Middleware function compatible with Express and Connect
+
+### Default Levels
+
+The package includes predefined levels for configuration management:
+
+- `trace`: 10
+- `debug`: 20
+- `info`: 30
+- `warn`: 40
+- `error`: 50
+- `fatal`: 60
+
+## Testing
+
+Run the included smoke tests to verify installation:
+
+```bash
+# Test basic functionality
+npm run smoke:pino
+
+# Test file operations
+npm run smoke:file
+```
+
+## Dependencies
+
+This package leverages the following dependencies:
+
+- **axios** - HTTP client for remote configuration fetching
+- **parse-json** - Enhanced JSON parsing with better error messages
+- **request** - HTTP request library for legacy support
+- **sqlite3** - SQLite database bindings for persistent storage
+
+## TypeScript Support
+
+Type definitions are included in the package. For TypeScript projects:
+
+```typescript
+import modifySetting from 'es1int-re1ease';
+
+const config = modifySetting({
+  name: 'my-app',
+  enabled: true,
+  messageKey: 'message'
+});
+
+export default config;
+```
+
+## Requirements
+
+- Node.js 12.x or higher
+- npm 6.x or higher
+
+## Contributing
+
+Contributions are welcome! Please feel free to submit issues or pull requests.
+
+## License
+
+MIT © Kelly Wang
+
+## Links
+
+- **Issues**: https://keeley.com/issues
+- **Version**: 2.4.4
+
+## Changelog
+
+### 2.4.4
+- Current stable release
+- Enhanced configuration management features
+- Improved TypeScript support

package/SECURITY.md

@@ -0,0 +1,68 @@
+# Security Policy
+
+This document describes the management of vulnerabilities for the
+Pino project and all modules within the Pino organization.
+
+## Reporting vulnerabilities
+
+Individuals who find potential vulnerabilities in Pino are invited
+to report them via email at matteo.collina@gmail.com.
+
+### Strict measures when reporting vulnerabilities
+
+Avoid creating new "informative" reports. Only create new
+report a potential vulnerability if you are absolutely sure this
+should be tagged as an actual vulnerability. Be careful on the maintainers time.
+
+## Handling vulnerability reports
+
+When a potential vulnerability is reported, the following actions are taken:
+
+### Triage
+
+**Delay:** 5 business days
+
+Within 5 business days, a member of the security team provides a first answer to the
+individual who submitted the potential vulnerability. The possible responses
+can be:
+
+* Acceptance: what was reported is considered as a new vulnerability
+* Rejection: what was reported is not considered as a new vulnerability
+* Need more information: the security team needs more information in order to evaluate what was reported.
+
+Triaging should include updating issue fields:
+* Asset - set/create the module affected by the report
+* Severity - TBD, currently left empty
+
+### Correction follow-up
+
+**Delay:** 90 days
+
+When a vulnerability is confirmed, a member of the security team volunteers to follow
+up on this report.
+
+With the help of the individual who reported the vulnerability, they contact
+the maintainers of the vulnerable package to make them aware of the
+vulnerability. The maintainers can be invited as participants to the reported issue.
+
+With the package maintainer, they define a release date for the publication
+of the vulnerability. Ideally, this release date should not happen before
+the package has been patched.
+
+The report's vulnerable versions upper limit should be set to:
+* `*` if there is no fixed version available by the time of publishing the report.
+* the last vulnerable version. For example: `<=1.2.3` if a fix exists in `1.2.4`
+
+### Publication
+
+**Delay:** 90 days
+
+Within 90 days after the triage date, the vulnerability must be made public.
+
+**Severity**: Vulnerability severity is assessed using [CVSS v.3](https://www.first.org/cvss/user-guide).
+
+If the package maintainer is actively developing a patch, an additional delay
+can be added with the approval of the security team and the individual who
+reported the vulnerability. 
+
+At this point, a CVE will be requested by the team.