Skip to content

chore: Remove package name to satisfy automated security checks #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Jakub Kadlubiec (jakubka) wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: Remove package name to satisfy automated security checks #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,4 @@
{
Copy link

Copilot AI Feb 24, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Removing the "name" and "version" fields from package.json may cause issues with npm tooling and package management. While technically valid for a non-published package, many npm commands and tools expect these fields to be present. Consider whether this is the correct approach to satisfy security checks. If the security concern is about exposing the package name "activities-stats", consider alternatives such as renaming the package or configuring the security scanning tool to exclude this repository. Could you clarify which specific security check requires this removal?

Suggested change
{
{
"name": "activities-stats",
"version": "1.0.0",

Copilot uses AI. Check for mistakes.
"name": "activities-stats",
"version": "1.0.0",
"scripts": {
"p1": "node p1.js",
"p2": "node p2/index.js"
Expand Down