@sitecore/sc-contenthub-blok 2.0.1 → 2.1.1

package/node_modules/path-type/readme.md

@@ -1,72 +0,0 @@
-# path-type [![Build Status](https://travis-ci.org/sindresorhus/path-type.svg?branch=master)](https://travis-ci.org/sindresorhus/path-type)
-
-> Check if a path is a file, directory, or symlink
-
-
-## Install
-
-```
-$ npm install path-type
-```
-
-
-## Usage
-
-```js
-const {isFile} = require('path-type');
-
-(async () => {
-	console.log(await isFile('package.json'));
-	//=> true
-})();
-```
-
-
-## API
-
-### isFile(path)
-
-Check whether the passed `path` is a file.
-
-Returns a `Promise<boolean>`.
-
-#### path
-
-Type: `string`
-
-The path to check.
-
-### isDirectory(path)
-
-Check whether the passed `path` is a directory.
-
-Returns a `Promise<boolean>`.
-
-### isSymlink(path)
-
-Check whether the passed `path` is a symlink.
-
-Returns a `Promise<boolean>`.
-
-### isFileSync(path)
-
-Synchronously check whether the passed `path` is a file.
-
-Returns a `boolean`.
-
-### isDirectorySync(path)
-
-Synchronously check whether the passed `path` is a directory.
-
-Returns a `boolean`.
-
-### isSymlinkSync(path)
-
-Synchronously check whether the passed `path` is a symlink.
-
-Returns a `boolean`.
-
-
-## License
-
-MIT © [Sindre Sorhus](https://sindresorhus.com)

package/node_modules/picocolors/LICENSE

@@ -1,15 +0,0 @@
-ISC License
-
-Copyright (c) 2021-2024 Oleksii Raspopov, Kostiantyn Denysov, Anton Verinov
-
-Permission to use, copy, modify, and/or distribute this software for any
-purpose with or without fee is hereby granted, provided that the above
-copyright notice and this permission notice appear in all copies.
-
-THE SOFTWARE IS PROVIDED "AS IS" AND THE AUTHOR DISCLAIMS ALL WARRANTIES
-WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF
-MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR
-ANY SPECIAL, DIRECT, INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES
-WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN
-ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
-OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.

package/node_modules/picocolors/README.md

@@ -1,21 +0,0 @@
-# picocolors
-
-The tiniest and the fastest library for terminal output formatting with ANSI colors.
-
-```javascript
-import pc from "picocolors"
-
-console.log(
-  pc.green(`How are ${pc.italic(`you`)} doing?`)
-)
-```
-
-- **No dependencies.**
-- **14 times** smaller and **2 times** faster than chalk.
-- Used by popular tools like PostCSS, SVGO, Stylelint, and Browserslist.
-- Node.js v6+ & browsers support. Support for both CJS and ESM projects.
-- TypeScript type declarations included.
-- [`NO_COLOR`](https://no-color.org/) friendly.
-
-## Docs
-Read **[full docs](https://github.com/alexeyraspopov/picocolors#readme)** on GitHub.

package/node_modules/picocolors/package.json

@@ -1,25 +0,0 @@
-{
-  "name": "picocolors",
-  "version": "1.1.1",
-  "main": "./picocolors.js",
-  "types": "./picocolors.d.ts",
-  "browser": {
-    "./picocolors.js": "./picocolors.browser.js"
-  },
-  "sideEffects": false,
-  "description": "The tiniest and the fastest library for terminal output formatting with ANSI colors",
-  "files": [
-    "picocolors.*",
-    "types.d.ts"
-  ],
-  "keywords": [
-    "terminal",
-    "colors",
-    "formatting",
-    "cli",
-    "console"
-  ],
-  "author": "Alexey Raspopov",
-  "repository": "alexeyraspopov/picocolors",
-  "license": "ISC"
-}

package/node_modules/picocolors/picocolors.browser.js

@@ -1,4 +0,0 @@
-var x=String;
-var create=function() {return {isColorSupported:false,reset:x,bold:x,dim:x,italic:x,underline:x,inverse:x,hidden:x,strikethrough:x,black:x,red:x,green:x,yellow:x,blue:x,magenta:x,cyan:x,white:x,gray:x,bgBlack:x,bgRed:x,bgGreen:x,bgYellow:x,bgBlue:x,bgMagenta:x,bgCyan:x,bgWhite:x,blackBright:x,redBright:x,greenBright:x,yellowBright:x,blueBright:x,magentaBright:x,cyanBright:x,whiteBright:x,bgBlackBright:x,bgRedBright:x,bgGreenBright:x,bgYellowBright:x,bgBlueBright:x,bgMagentaBright:x,bgCyanBright:x,bgWhiteBright:x}};
-module.exports=create();
-module.exports.createColors = create;

package/node_modules/picocolors/picocolors.d.ts

@@ -1,5 +0,0 @@
-import { Colors } from "./types"
-
-declare const picocolors: Colors & { createColors: (enabled?: boolean) => Colors }
-
-export = picocolors

package/node_modules/picocolors/picocolors.js

@@ -1,75 +0,0 @@
-let p = process || {}, argv = p.argv || [], env = p.env || {}
-let isColorSupported =
-	!(!!env.NO_COLOR || argv.includes("--no-color")) &&
-	(!!env.FORCE_COLOR || argv.includes("--color") || p.platform === "win32" || ((p.stdout || {}).isTTY && env.TERM !== "dumb") || !!env.CI)
-
-let formatter = (open, close, replace = open) =>
-	input => {
-		let string = "" + input, index = string.indexOf(close, open.length)
-		return ~index ? open + replaceClose(string, close, replace, index) + close : open + string + close
-	}
-
-let replaceClose = (string, close, replace, index) => {
-	let result = "", cursor = 0
-	do {
-		result += string.substring(cursor, index) + replace
-		cursor = index + close.length
-		index = string.indexOf(close, cursor)
-	} while (~index)
-	return result + string.substring(cursor)
-}
-
-let createColors = (enabled = isColorSupported) => {
-	let f = enabled ? formatter : () => String
-	return {
-		isColorSupported: enabled,
-		reset: f("\x1b[0m", "\x1b[0m"),
-		bold: f("\x1b[1m", "\x1b[22m", "\x1b[22m\x1b[1m"),
-		dim: f("\x1b[2m", "\x1b[22m", "\x1b[22m\x1b[2m"),
-		italic: f("\x1b[3m", "\x1b[23m"),
-		underline: f("\x1b[4m", "\x1b[24m"),
-		inverse: f("\x1b[7m", "\x1b[27m"),
-		hidden: f("\x1b[8m", "\x1b[28m"),
-		strikethrough: f("\x1b[9m", "\x1b[29m"),
-
-		black: f("\x1b[30m", "\x1b[39m"),
-		red: f("\x1b[31m", "\x1b[39m"),
-		green: f("\x1b[32m", "\x1b[39m"),
-		yellow: f("\x1b[33m", "\x1b[39m"),
-		blue: f("\x1b[34m", "\x1b[39m"),
-		magenta: f("\x1b[35m", "\x1b[39m"),
-		cyan: f("\x1b[36m", "\x1b[39m"),
-		white: f("\x1b[37m", "\x1b[39m"),
-		gray: f("\x1b[90m", "\x1b[39m"),
-
-		bgBlack: f("\x1b[40m", "\x1b[49m"),
-		bgRed: f("\x1b[41m", "\x1b[49m"),
-		bgGreen: f("\x1b[42m", "\x1b[49m"),
-		bgYellow: f("\x1b[43m", "\x1b[49m"),
-		bgBlue: f("\x1b[44m", "\x1b[49m"),
-		bgMagenta: f("\x1b[45m", "\x1b[49m"),
-		bgCyan: f("\x1b[46m", "\x1b[49m"),
-		bgWhite: f("\x1b[47m", "\x1b[49m"),
-
-		blackBright: f("\x1b[90m", "\x1b[39m"),
-		redBright: f("\x1b[91m", "\x1b[39m"),
-		greenBright: f("\x1b[92m", "\x1b[39m"),
-		yellowBright: f("\x1b[93m", "\x1b[39m"),
-		blueBright: f("\x1b[94m", "\x1b[39m"),
-		magentaBright: f("\x1b[95m", "\x1b[39m"),
-		cyanBright: f("\x1b[96m", "\x1b[39m"),
-		whiteBright: f("\x1b[97m", "\x1b[39m"),
-
-		bgBlackBright: f("\x1b[100m", "\x1b[49m"),
-		bgRedBright: f("\x1b[101m", "\x1b[49m"),
-		bgGreenBright: f("\x1b[102m", "\x1b[49m"),
-		bgYellowBright: f("\x1b[103m", "\x1b[49m"),
-		bgBlueBright: f("\x1b[104m", "\x1b[49m"),
-		bgMagentaBright: f("\x1b[105m", "\x1b[49m"),
-		bgCyanBright: f("\x1b[106m", "\x1b[49m"),
-		bgWhiteBright: f("\x1b[107m", "\x1b[49m"),
-	}
-}
-
-module.exports = createColors()
-module.exports.createColors = createColors

package/node_modules/picocolors/types.d.ts

@@ -1,51 +0,0 @@
-export type Formatter = (input: string | number | null | undefined) => string
-
-export interface Colors {
-	isColorSupported: boolean
-
-	reset: Formatter
-	bold: Formatter
-	dim: Formatter
-	italic: Formatter
-	underline: Formatter
-	inverse: Formatter
-	hidden: Formatter
-	strikethrough: Formatter
-
-	black: Formatter
-	red: Formatter
-	green: Formatter
-	yellow: Formatter
-	blue: Formatter
-	magenta: Formatter
-	cyan: Formatter
-	white: Formatter
-	gray: Formatter
-
-	bgBlack: Formatter
-	bgRed: Formatter
-	bgGreen: Formatter
-	bgYellow: Formatter
-	bgBlue: Formatter
-	bgMagenta: Formatter
-	bgCyan: Formatter
-	bgWhite: Formatter
-
-	blackBright: Formatter
-	redBright: Formatter
-	greenBright: Formatter
-	yellowBright: Formatter
-	blueBright: Formatter
-	magentaBright: Formatter
-	cyanBright: Formatter
-	whiteBright: Formatter
-
-	bgBlackBright: Formatter
-	bgRedBright: Formatter
-	bgGreenBright: Formatter
-	bgYellowBright: Formatter
-	bgBlueBright: Formatter
-	bgMagentaBright: Formatter
-	bgCyanBright: Formatter
-	bgWhiteBright: Formatter
-}

package/node_modules/resolve/.claude/notes.md

@@ -1,26 +0,0 @@
-# resolve package - session notes
-
-## Versioning
-- Manual versioning only - do NOT use `npm version`
-- Edit package.json version directly, commit with message `v{version}`, then create annotated tag
-- Changelog lives in git tag annotations, not a separate file
-- Tag format: `git tag -a v{version} -m "{changelog}"`
-
-## Code style
-- `__proto__: null` on ALL object literals (prototype pollution protection)
-- `.slice()` not `.substring()`
-- One exported function per file
-- Move nested/inner functions to module level when feasible
-- Prefer non-hoisted declarations (function declarations at module level, not expressions)
-- No mutation - copy objects instead of modifying inputs
-
-## Testing
-- `test/list-exports` is a git submodule with sparse checkout
-- Tests should cover ALL entrypoints from fixtures, not just `'.'` subpaths
-- Use `extensions: ['.js', '.json']` when testing exports resolution
-
-## exports field implementation
-- Uses `node-exports-info` for category semantics
-- Categories: pre-exports, broken, conditions, patterns, pattern-trailers, current
-- `exportsCategory` option or `engines: true` to auto-detect from consumer's engines.node
-- Self-reference resolution respects node_modules boundaries

package/node_modules/resolve/.claude/settings.local.json

@@ -1,26 +0,0 @@
-{
-  "permissions": {
-    "allow": [
-      "WebFetch(domain:github.com)",
-      "WebSearch",
-      "WebFetch(domain:raw.githubusercontent.com)",
-      "WebFetch(domain:api.github.com)",
-      "WebFetch(domain:www.npmjs.com)",
-      "Bash(tree:*)",
-      "Bash(find:*)",
-      "Bash(npm view:*)",
-      "Bash(node test/resolver_sync.js:*)",
-      "Bash(xxd:*)",
-      "Bash(npm info:*)",
-      "Bash(grep:*)",
-      "Bash(npm run submodule:update:*)",
-      "Bash(git rev-parse:*)",
-      "Bash(git -C test/list-exports diff packages/tests/fixtures/resolve-2/project/test/resolver/nested_symlinks/mylib/async.js)",
-      "Bash(gh run list:*)",
-      "Bash(ls:*)",
-      "Bash(tape test/homedir.js)",
-      "Bash(tape test/default_paths.js)",
-      "Bash(tape test/mock.js)"
-    ]
-  }
-}

package/node_modules/resolve/.editorconfig

@@ -1,38 +0,0 @@
-root = true
-
-[*]
-indent_style = space
-indent_size = 2
-end_of_line = lf
-charset = utf-8
-trim_trailing_whitespace = true
-insert_final_newline = true
-max_line_length = 200
-
-[*.{,m}js]
-block_comment_start = /*
-block_comment = *
-block_comment_end = */
-
-[*.yml]
-indent_style = space
-indent_size = 1
-
-[{package.json,*.mjs}]
-indent_style = tab
-
-[lib/core.json]
-indent_style = tab
-
-[CHANGELOG.md]
-indent_style = space
-indent_size = 2
-
-[{*.json,Makefile,CONTRIBUTING.md}]
-max_line_length = off
-
-[test/{dotdot,resolver,module_dir,multirepo,node_path,pathfilter,precedence}/**/*]
-indent_style = off
-indent_size = off
-max_line_length = off
-insert_final_newline = off

package/node_modules/resolve/.eslintrc

@@ -1,65 +0,0 @@
-{
-    "root": true,
-
-    "extends": "@ljharb",
-
-    "rules": {
-        "indent": [2, 4],
-        "strict": 0,
-        "complexity": 0,
-        "consistent-return": 0,
-        "curly": 0,
-        "dot-notation": [2, { "allowKeywords": true }],
-        "func-name-matching": 0,
-        "func-style": 0,
-        "global-require": 1,
-        "id-length": [2, { "min": 1, "max": 40 }],
-        "max-lines": [2, 360],
-        "max-lines-per-function": 0,
-        "max-nested-callbacks": 0,
-        "max-params": 0,
-        "max-statements-per-line": [2, { "max": 2 }],
-        "max-statements": 0,
-        "no-magic-numbers": 0,
-        "no-shadow": 0,
-        "no-use-before-define": 0,
-        "sort-keys": 0,
-    },
-    "overrides": [
-        {
-            "files": "bin/**",
-            "rules": {
-                "no-process-exit": "off",
-            },
-        },
-        {
-            "files": "example/**",
-            "rules": {
-                "no-console": 0,
-            },
-        },
-        {
-            "files": "test/resolver/nested_symlinks/mylib/*.js",
-            "rules": {
-                "no-throw-literal": 0,
-            },
-        },
-        {
-            "files": "test/**",
-            "parserOptions": {
-                "ecmaVersion": 5,
-                "allowReserved": false,
-            },
-            "rules": {
-                "dot-notation": [2, { "allowPattern": "throws" }],
-                "max-lines": 0,
-                "max-lines-per-function": 0,
-                "no-unused-vars": [2, { "vars": "all", "args": "none" }],
-            },
-        },
-    ],
-
-    "ignorePatterns": [
-        "./test/resolver/malformed_package_json/package.json",
-    ],
-}

package/node_modules/resolve/.github/FUNDING.yml

@@ -1,12 +0,0 @@
-# These are supported funding model platforms
-
-github: [ljharb]
-patreon: # Replace with a single Patreon username
-open_collective: # Replace with a single Open Collective username
-ko_fi: # Replace with a single Ko-fi username
-tidelift: npm/resolve
-community_bridge: # Replace with a single Community Bridge project-name e.g., cloud-foundry
-liberapay: # Replace with a single Liberapay username
-issuehunt: # Replace with a single IssueHunt username
-otechie: # Replace with a single Otechie username
-custom: # Replace with up to 4 custom sponsorship URLs e.g., ['link1', 'link2']

package/node_modules/resolve/.github/INCIDENT_RESPONSE_PROCESS.md

@@ -1,119 +0,0 @@
-# Incident Response Process for **resolve**
-
-## Reporting a Vulnerability
-
-We take the security of **resolve** very seriously. If you believe you’ve found a security vulnerability, please inform us responsibly through coordinated disclosure.
-
-### How to Report
-
-> **Do not** report security vulnerabilities through public GitHub issues, discussions, or social media.
-
-Instead, please use one of these secure channels:
-
-1. **GitHub Security Advisories**
-   Use the **Report a vulnerability** button in the Security tab of the [browserify/resolve repository](https://github.com/browserify/resolve).
-
-2. **Email**
-   Follow the posted [Security Policy](https://github.com/browserify/resolve/security/policy).
-
-### What to Include
-
-**Required Information:**
-- Brief description of the vulnerability type
-- Affected version(s) and components
-- Steps to reproduce the issue
-- Impact assessment (what an attacker could achieve)
-- Confirm the issue is not present in test files (in other words, only via the official entry points in `exports`)
-
-**Helpful Additional Details:**
-- Full paths of affected source files
-- Specific commit or branch where the issue exists
-- Required configuration to reproduce
-- Proof-of-concept code (if available)
-- Suggested mitigation or fix
-
-## Our Response Process
-
-**Timeline Commitments:**
-- **Initial acknowledgment**: Within 24 hours
-- **Detailed response**: Within 3 business days
-- **Status updates**: Every 7 days until resolved
-- **Resolution target**: 90 days for most issues
-
-**What We’ll Do:**
-1. Acknowledge your report and assign a tracking ID
-2. Assess the vulnerability and determine severity
-3. Develop and test a fix
-4. Coordinate disclosure timeline with you
-5. Release a security update and publish an advisory and CVE
-6. Credit you in our security advisory (if desired)
-
-## Disclosure Policy
-
-- **Coordinated disclosure**: We’ll work with you on timing
-- **Typical timeline**: 90 days from report to public disclosure
-- **Early disclosure**: If actively exploited
-- **Delayed disclosure**: For complex issues
-
-## Scope
-
-**In Scope:**
-- **resolve** package (all supported versions)
-- Official examples and documentation
-- Core resolution APIs
-- Dependencies with direct security implications
-
-**Out of Scope:**
-- Third-party wrappers or extensions
-- Bundler-specific integrations
-- Social engineering or physical attacks
-- Theoretical vulnerabilities without practical exploitation
-- Issues in non-production files
-
-## Security Measures
-
-**Our Commitments:**
-- Regular vulnerability scanning via `npm audit`
-- Automated security checks in CI/CD (GitHub Actions)
-- Secure coding practices and mandatory code review
-- Prompt patch releases for critical issues
-
-**User Responsibilities:**
-- Keep **resolve** updated
-- Monitor dependency vulnerabilities
-- Follow secure configuration guidelines for module resolution
-
-## Legal Safe Harbor
-
-**We will NOT:**
-- Initiate legal action
-- Contact law enforcement
-- Suspend or terminate your access
-
-**You must:**
-- Only test against your own installations
-- Not access, modify, or delete user data
-- Not degrade service availability
-- Not publicly disclose before coordinated disclosure
-- Act in good faith
-
-## Recognition
-
-- **Advisory Credits**: Credit in GitHub Security Advisories (unless anonymous)
-
-## Security Updates
-
-**Stay Informed:**
-- Subscribe to npm updates for **resolve**
-- Enable GitHub Security Advisory notifications
-
-**Update Process:**
-- Patch releases (e.g., 1.22.10 → 1.22.11)
-- Out-of-band releases for critical issues
-- Advisories via GitHub Security Advisories
-
-## Contact Information
-
-- **Security reports**: Security tab of [browserify/resolve](https://github.com/browserify/resolve/security)
-- **General inquiries**: GitHub Discussions or Issues
-

package/node_modules/resolve/.github/THREAT_MODEL.md

@@ -1,74 +0,0 @@
-## Threat Model for resolve (module path resolution library)
-
-### 1. Library Overview
-
-- **Library Name:** resolve
-- **Brief Description:** Implements Node.js `require.resolve()` algorithm for synchronous and asynchronous file path resolution. Used to locate modules and files in Node.js projects.
-- **Key Public APIs/Functions:** `resolve.sync()` / `resolve/sync`, `resolve()` / `resolve/async`
-
-### 2. Define Scope
-
-This threat model focuses on the core path resolution algorithm, including filesystem interaction, option handling, and cache management.
-
-### 3. Conceptual System Diagram
-
-```
-Caller Application → resolve(id, options) → Resolution Algorithm → File System
-                           │
-                           └→ Options Handling
-                           └→ Cache System
-```
-
-**Trust Boundaries:**
-- **Input module IDs:** May come from untrusted sources (user input, configuration)
-- **Filesystem access:** The library interacts with the filesystem to resolve paths
-- **Options:** Provided by the caller
-- **Cache:** Used to improve performance, but could be a vector for tampering or information disclosure if not handled securely
-
-### 4. Identify Assets
-
-- **Integrity of resolution output:** Ensure correct and safe file path matching.
-- **Confidentiality of configuration:** Prevent sensitive path information from being leaked.
-- **Availability/performance for host application:** Prevent crashes or resource exhaustion.
-- **Security of host application:** Prevent path traversal or unintended filesystem access.
-- **Reputation of library:** Maintain trust by avoiding supply chain attacks and vulnerabilities[1][3][4].
-
-### 5. Identify Threats
-
-| Component / API / Interaction                       | S  | T  | R  | I  | D  | E  |
-|-----------------------------------------------------|----|----|----|----|----|----|
-| Public API Call (`resolve/async`, `resolve/sync`)   | ✓  | ✓  | –  | ✓  | –  | –  |
-| Filesystem Access                                   | –  | ✓  | –  | ✓  | ✓  | –  |
-| Options Handling                                    | ✓  | ✓  | –  | ✓  | –  | –  |
-| Cache System                                        | –  | ✓  | –  | ✓  | –  | –  |
-
-**Key Threats:**
-- **Spoofing:** Malicious module IDs mimicking legitimate packages, or spoofing configuration options[1].
-- **Tampering:** Caller-provided paths altering resolution order, or cache tampering leading to incorrect results[1][4].
-- **Information Disclosure:** Error messages revealing filesystem structure or sensitive paths[1].
-- **Denial of Service:** Recursive or excessive resolution exhausting filesystem handles or causing application crashes[1].
-- **Path Traversal:** Malicious input allowing access to files outside the intended directory[4].
-
-### 6. Mitigation/Countermeasures
-
-| Threat Identified                          | Proposed Mitigation |
-|--------------------------------------------|---------------------|
-| Spoofing (malicious module IDs/config)     | Sanitize input IDs; validate against known patterns; restrict `basedir` to app-controlled paths[1][4]. |
-| Tampering (path traversal, cache)          | Validate input IDs for directory escapes; secure cache reads/writes; restrict cache to trusted sources[1][4]. |
-| Information Disclosure (error messages)    | Generic "not found" errors without internal paths; avoid exposing sensitive configuration in errors[1]. |
-| Denial of Service (resource exhaustion)    | Limit recursive resolution depth; implement timeout; monitor for excessive filesystem operations[1]. |
-
-### 7. Risk Ranking
-
-- **High:** Path traversal via malicious IDs (if not properly mitigated)
-- **Medium:** Cache tampering or spoofing (if cache is not secured)
-- **Low:** Information disclosure in errors (if error handling is generic)
-
-### 8. Next Steps & Review
-
-1. **Implement input sanitization for module IDs and configuration.**
-2. **Add resolution depth limiting and timeout.**
-3. **Audit cache handling for race conditions and tampering.**
-4. **Regularly review dependencies for vulnerabilities.**
-5. **Keep documentation and threat model up to date.**
-6. **Monitor for new threats as the ecosystem and library evolve[1][3].**

package/node_modules/resolve/LICENSE

@@ -1,21 +0,0 @@
-MIT License
-
-Copyright (c) 2012 James Halliday
-
-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/node_modules/resolve/SECURITY.md

@@ -1,13 +0,0 @@
-# Security
-
-Please [file a private vulnerability report](https://github.com/browserify/resolve/security/advisories/new),
-or email [@ljharb](https://github.com/ljharb),
-if you have a potential security vulnerability to report.
-
-## Incident Response
-
-See our [Incident Response Process](.github/INCIDENT_RESPONSE_PROCESS.md).
-
-## Threat Model
-
-See [THREAT_MODEL.md](./THREAT_MODEL.md).