Skip to content

Security Hardening#264

Merged
shgysk8zer0 merged 2 commits into
masterfrom
feature/ci-security
Jun 15, 2026
Merged

Security Hardening#264
shgysk8zer0 merged 2 commits into
masterfrom
feature/ci-security

Conversation

@shgysk8zer0

Copy link
Copy Markdown
Member

Added

  • Add Security policy
  • Add npm config to harden installs

Changed

  • Update Workflows with permissions
  • Update contributiing guidelines
  • Update to node 26.3.0 & npm 11.16.0

Description and issue

Please add relevant sections (Added, removed, changed, fixed) to CHANGELOG.md

List of significant changes made

### Added
- Add Security policy
- Add npm config to harden installs

### Changed
- Update Workflows with permissions
- Update contributiing guidelines
- Update to node 26.3.0 & npm 11.16.0
@shgysk8zer0 shgysk8zer0 self-assigned this Jun 15, 2026
@shgysk8zer0 shgysk8zer0 added the enhancement New feature or request label Jun 15, 2026
@shgysk8zer0 shgysk8zer0 enabled auto-merge June 15, 2026 16:49
@socket-security

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm js-yaml is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package-lock.jsonnpm/@shgysk8zer0/importmap@1.10.1npm/js-yaml@4.2.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/js-yaml@4.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@shgysk8zer0 shgysk8zer0 merged commit b026970 into master Jun 15, 2026
8 checks passed
@shgysk8zer0 shgysk8zer0 deleted the feature/ci-security branch June 15, 2026 16:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant