feat: replace keytar with @github/keytar

[congminh1254]

No description provided.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​@​github/​keytar@​7.10.6
	npm/​@​oclif/​plugin-not-found@​3.2.86 ⏵ 3.2.87				+2
	npm/​box-node-sdk@​4.11.0 ⏵ 4.11.1				+1
	npm/​@​oclif/​plugin-help@​6.2.49 ⏵ 6.2.50				+2
	npm/​@​oclif/​plugin-version@​2.2.46 ⏵ 2.2.47				+1
	npm/​js-yaml@​4.1.1 ⏵ 4.2.0	-3		+1	+1
	npm/​baseline-browser-mapping@​2.10.32 ⏵ 2.10.33
	npm/​oclif@​4.23.8 ⏵ 4.23.10	+1			+1

View full report

[coveralls]

Coverage Report for CI Build 26748832470

Coverage decreased (-0.005%) to 84.967%

Details

• Coverage decreased (-0.005%) from the base build.
• Patch coverage: 3 uncovered changes across 1 file (18 of 21 lines covered, 85.71%).
• No coverage regressions found.

Uncovered Changes

File	Changed	Covered	%
src/secure-storage.js	21	18	85.71%

Coverage Regressions

No coverage regressions found.

---

Coverage Stats

Relevant Lines:	6051
Covered Lines:	5392
Line Coverage:	89.11%
Relevant Branches:	2151
Covered Branches:	1577
Branch Coverage:	73.31%
Branches in Coverage %:	Yes
Coverage Strength:	643.35 hits per line

---

💛 - Coveralls

[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 js-yaml is 85.0% likely obfuscated Confidence: 0.85 Location: Package overview From: package-lock.json → npm/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

[arjankowski]

Could you add some logs here via DEBUG.init ?

[congminh1254]

I added the logs, it will only show up when run something like:

DEBUG=box-cli:*  ./bin/run users:get 

but not

./bin/run users:get  --verbose

because at the moment we parse the verbose flag, the log already emitted.

[arjankowski]

lgtm