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).

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.

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.

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