Update examples to use @keeper-security/keeperapi 17.1.0

[tylerccarson]

Replaces old keeperapi 0.2.0 (which depended on crypto-js) in the browser example and bumps the node example from 16.0.5 to 17.1.0.

[socket-security]

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

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​keeper-security/​keeperapi@​16.0.5 ⏵ 17.1.0	-2		+4	+6

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 @keeper-security/keeperapi is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: examples/print-vault-node/package.json → npm/@keeper-security/keeperapi@17.1.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/@keeper-security/keeperapi@17.1.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