Skip to content

refactor: use Tempo API for token metadata#71

Closed
decofe wants to merge 2 commits into
mainfrom
centaur/migrate-tempo-api-20260714143203
Closed

refactor: use Tempo API for token metadata#71
decofe wants to merge 2 commits into
mainfrom
centaur/migrate-tempo-api-20260714143203

Conversation

@decofe

@decofe decofe commented Jul 14, 2026

Copy link
Copy Markdown
Member

Summary

  • fetch TIP-20 metadata with the tapimo typed client
  • support a configurable TEMPO_API_URL while defaulting to https://api.tempo.xyz
  • retain localnet and request-failure fallbacks

Validation

  • pnpm check
  • pnpm check:types
  • ./node_modules/.bin/vp test src/lib/tempo.test.ts --project unit (7 passed)
  • pnpm test blocked in global setup: local Tempo container returned HTTP 400 while minting the fee payer

Prompted by: @tmm

@socket-security

Copy link
Copy Markdown

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

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Addedtapimo@​0.3.0661009999100

View full report

@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
Protestware or unwanted behavior: npm es5-ext

Note: The script attempts to run a local post-install script, which could potentially contain malicious code. The error handling suggests that it is designed to fail silently, which is a common tactic in malicious scripts.

From: pnpm-lock.yamlnpm/tapimo@0.3.0npm/es5-ext@0.10.64

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

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: Consider that consuming this package may come along with functionality unrelated to its primary purpose.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/es5-ext@0.10.64. 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

@tmm tmm closed this Jul 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants