Add package protection

[metajinglun]

Summary

• add Bun exact-install and Socket scanner config
• add repository guard checks for exact dependency versions, minimum package age, phantom deps, and sensitive Solana/API diffs
• add package-protection GitHub Action, CODEOWNERS, and branch protection docs
• update lockfile and pin tooling dependencies

Validation

• bun run repo:guard
• bun run deps:check
• bun install --frozen-lockfile
• bun run typecheck

[github-actions]

Package Protection

• Lockfile + Socket scan: pass
• Repo guard: pass
• Phantom deps: pass

Repository Guard

Exact dependency versions

• Status: pass
• All dependencies, devDependencies, optionalDependencies, and peerDependencies use exact versions or workspace:*.

Package minimum age

• Status: pass
• All pinned external packages are at least 14 days old.

Sensitive wallet / program changes

• Status: pass
• No suspicious wallet routing, signing-path, or program-ID changes were detected in this PR diff.

Overall status: pass

Transitive supply-chain threats are covered by the Socket scanner (via @socketsecurity/bun-security-scanner in bunfig.toml), which runs on every bun install. This guard blocks merge on direct-dep pinning and age policy; the sensitive-diff section is a review hint, not a merge gate (CODEOWNERS handles the actual review requirement).

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	knip@​6.3.0
	@​socketsecurity/​bun-security-scanner@​1.1.2

View full report

[socket-security]

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		Obfuscated code: npm formatly is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → npm/knip@6.3.0 → npm/formatly@0.3.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/formatly@0.3.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