@dynamic-labs/sdk-react-core
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Established SDK, not a spam/phishing package. | ai | |
| semgrep | semgrep:shady-links-tlds | AI (semgrep): dynamic.xyz is the package's own homepage domain; not a C2/exfiltration URL. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Base64 decode is used for session key deserialization from storage; no exfiltration path. | ai |
Versions (showing 73 of 73)
| Version | Deps | Published |
|---|---|---|
| 4.93.1 | 28 / 1 | |
| 4.93.0 | 28 / 1 | |
| 4.92.4 | 28 / 1 | |
| 4.92.3 | 28 / 1 | |
| 4.92.2 | 28 / 1 | |
| 4.92.1 | 28 / 1 | |
| 4.92.0 | 28 / 1 | |
| 4.91.6 | 27 / 1 | |
| 4.91.5 | 27 / 1 | |
| 4.91.4 | 27 / 1 | |
| 4.91.3 | 27 / 1 | |
| 4.91.2 | 27 / 1 | |
| 4.91.1 | 27 / 1 | |
| 4.91.0 | 27 / 1 | |
| 4.90.0 | 27 / 1 | |
| 4.89.0 | 27 / 1 | |
| 4.88.6 | 27 / 1 | |
| 4.88.5 | 27 / 1 | |
| 4.88.4 | 27 / 1 | |
| 4.88.3 | 27 / 1 | |
| 4.88.2 | 27 / 1 | |
| 4.88.1 | 27 / 1 | |
| 4.88.0 | 27 / 1 | |
| 4.87.2 | 27 / 1 | |
| 4.87.1 | 27 / 1 | |
| 4.87.0 | 27 / 1 | |
| 4.86.0 | 27 / 1 | |
| 4.85.0 | 27 / 1 | |
| 4.84.1 | 27 / 1 | |
| 4.84.0 | 27 / 1 | |
| 4.83.1 | 27 / 1 | |
| 4.83.0 | 26 / 1 | |
| 4.82.0 | 26 / 1 | |
| 4.81.0 | 26 / 1 | |
| 4.80.0 | 26 / 1 | |
| 4.79.2 | 26 / 1 | |
| 4.79.1 | 26 / 1 | |
| 4.79.0 | 26 / 1 | |
| 4.78.1 | 26 / 1 | |
| 4.78.0 | 26 / 1 | |
| 4.77.4 | 26 / 1 | |
| 4.77.3 | 26 / 1 | |
| 4.77.2 | 26 / 1 | |
| 4.77.1 | 26 / 1 | |
| 4.77.0 | 26 / 1 | |
| 4.76.0 | 26 / 1 | |
| 4.75.0 | 26 / 1 | |
| 4.74.1 | 26 / 1 | |
| 4.61.2 | 26 / 1 | |
| 4.60.0 | 26 / 1 | |
| 4.49.0 | 25 / 1 | |
| 4.48.2 | 25 / 1 | |
| 4.48.1 | 25 / 1 | |
| 4.48.0 | 25 / 1 | |
| 4.47.3 | 25 / 1 | |
| 4.47.2 | 25 / 1 | |
| 4.47.1 | 25 / 1 | |
| 4.47.0 | 25 / 1 | |
| 4.46.3 | 25 / 1 | |
| 4.46.2 | 25 / 1 | |
| 4.46.1 | 25 / 1 | |
| 4.46.0 | 25 / 1 | |
| 4.45.3 | 25 / 1 | |
| 4.45.2 | 25 / 1 | |
| 4.45.1 | 25 / 1 | |
| 4.45.0 | 25 / 1 | |
| 4.44.4 | 25 / 1 | |
| 4.44.3 | 25 / 1 | |
| 4.44.2 | 25 / 1 | |
| 4.44.1 | 25 / 1 | |
| 4.44.0 | 25 / 1 | |
| 4.43.0 | 25 / 1 | |
| 4.42.0 | 25 / 1 |
v4.93.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.93.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.92.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.91.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.2
2 findingsThis version was published by a different npm account than previous versions on 2026-02-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.60.0
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.49.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.48.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.48.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.48.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.47.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.47.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.47.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.47.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.46.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.45.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.45.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.45.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.45.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.44.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.43.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.42.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.