@dynamic-labs/tempo
A React SDK for implementing Tempo wallet web3 authentication and authorization to your website.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Transition from packaging-at-dynamic-labs to GitHub Actions reflects CI/CD automation; consistent with org-wide publishing migration. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Dynamic Labs org uses 0.0.0 as a namespace placeholder; consistent with their publishing pattern. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Placeholder/namespace reservation by established Dynamic Labs publisher; not spam or malware. | ai | |
| provenance | no-provenance | AI (provenance): Dynamic Labs publishes via GitHub Actions without Sigstore attestation; consistent across the SDK family. | ai |
Versions (showing 33 of 33)
| Version | Deps | Published |
|---|---|---|
| 4.88.1 | 9 / 0 | |
| 4.88.0 | 9 / 0 | |
| 4.87.2 | 9 / 0 | |
| 4.87.1 | 9 / 0 | |
| 4.87.0 | 9 / 0 | |
| 4.86.0 | 9 / 0 | |
| 4.85.0 | 9 / 0 | |
| 4.84.1 | 9 / 0 | |
| 4.84.0 | 9 / 0 | |
| 4.83.1 | 9 / 0 | |
| 4.83.0 | 9 / 0 | |
| 4.82.0 | 9 / 0 | |
| 4.81.0 | 9 / 0 | |
| 4.80.0 | 9 / 0 | |
| 4.79.2 | 9 / 0 | |
| 4.79.1 | 9 / 0 | |
| 4.79.0 | 9 / 0 | |
| 4.78.1 | 9 / 0 | |
| 4.78.0 | 9 / 0 | |
| 4.77.4 | 9 / 0 | |
| 4.77.3 | 9 / 0 | |
| 4.77.2 | 9 / 0 | |
| 4.77.1 | 9 / 0 | |
| 4.77.0 | 9 / 0 | |
| 4.76.0 | 9 / 0 | |
| 4.75.0 | 9 / 0 | |
| 4.74.1 | 9 / 0 | |
| 4.74.0 | 9 / 0 | |
| 4.73.2 | 9 / 0 | |
| 4.73.0 | 9 / 0 | |
| 4.72.0 | 9 / 0 | |
| 4.71.0 | 9 / 0 | |
| 0.0.0 | 0 / 0 |
v4.88.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.88.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.84.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.84.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.83.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.83.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.81.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.80.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.79.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.79.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.79.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.78.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.78.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.77.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.77.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.77.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.77.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.77.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.76.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.75.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.74.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.74.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.73.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.73.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.72.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-26. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.71.0
2 findingsThis version was published by a different npm account than previous versions on 2026-03-24. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.