Potential security issue detected: Your extension package contains sensitive information that should not be published. Please remove these secrets before packaging. found npm access token: npm_Ab3kZy0X9QpLmN4tUvW7aB... [npm] src/test/fixtures/secrets/secret2.ts#1:19-1:59 In case of false positives, you can allow specific types of secrets with --allow-package-secrets npm or use --allow-package-all-secrets to skip this check entirely (not recommended).

Potential security issue detected: Your extension package contains sensitive information that should not be published. Please remove these secrets before packaging. found private key: -----BEGIN OPENSSH PRIVATE KEY-... [privatekey] src/test/fixtures/secrets/secret1.ts#2:1-9:34 In case of false positives, you can allow specific types of secrets with --allow-package-secrets privatekey or use --allow-package-all-secrets to skip this check entirely (not recommended).

.env files should not be packaged. Do not include the file in your package.json files property. To ignore this check, you can use --allow-package-env-file (not recommended).

Potential security issue detected: Your extension package contains sensitive information that should not be published. Please remove these secrets before packaging. found npm access token: npm_Ab3kZy0X9QpLmN4tUvW7aB... [npm] src/test/fixtures/secrets/secret2.ts#1:19-1:59 In case of false positives, you can allow specific types of secrets with --allow-package-secrets npm or use --allow-package-all-secrets to skip this check entirely (not recommended).

Potential security issue detected: Your extension package contains sensitive information that should not be published. Please remove these secrets before packaging. found private key: -----BEGIN OPENSSH PRIVATE KEY-... [privatekey] src/test/fixtures/secrets/secret1.ts#2:1-9:34 In case of false positives, you can allow specific types of secrets with --allow-package-secrets privatekey or use --allow-package-all-secrets to skip this check entirely (not recommended).

.env files should not be packaged. Do not include the file in your package.json files property. To ignore this check, you can use --allow-package-env-file (not recommended).

Potential security issue detected: Your extension package contains sensitive information that should not be published. Please remove these secrets before packaging. found npm access token: npm_Ab3kZy0X9QpLmN4tUvW7aB... [npm] src\test\fixtures\secrets\secret2.ts#1:19-1:59 In case of false positives, you can allow specific types of secrets with --allow-package-secrets npm or use --allow-package-all-secrets to skip this check entirely (not recommended).

Potential security issue detected: Your extension package contains sensitive information that should not be published. Please remove these secrets before packaging. found private key: -----BEGIN OPENSSH PRIVATE KEY-... [privatekey] src\test\fixtures\secrets\secret1.ts#2:1-9:34 In case of false positives, you can allow specific types of secrets with --allow-package-secrets privatekey or use --allow-package-all-secrets to skip this check entirely (not recommended).

.env files should not be packaged. Do not include the file in your package.json files property. To ignore this check, you can use --allow-package-env-file (not recommended).

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

LICENSE, LICENSE.md, or LICENSE.txt not found

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

LICENSE, LICENSE.md, or LICENSE.txt not found

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

LICENSE, LICENSE.md, or LICENSE.txt not found

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

LICENSE, LICENSE.md, or LICENSE.txt not found

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

LICENSE, LICENSE.md, or LICENSE.txt not found

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

LICENSE, LICENSE.md, or LICENSE.txt not found

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4, actions/setup-node@v4. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

LICENSE, LICENSE.md, or LICENSE.txt not found

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

LICENSE, LICENSE.md, or LICENSE.txt not found

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.

LICENSE, LICENSE.md, or LICENSE.txt not found

A 'repository' field is missing from the 'package.json' manifest file. Use --allow-missing-repository to bypass.