@dynamic-labs/flow
A React SDK for implementing 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): Dynamic Labs migrated publishing to GitHub Actions CI; consistent with org-wide CI/CD adoption across their 852-version package history. | ai | |
| dependencies | unvetted-dep:@onflow/fcl | AI (dependencies): @onflow/fcl is the official Flow blockchain client; expected and stable dependency for this Flow wallet connector package. | ai | |
| provenance | no-provenance | AI (provenance): Established Dynamic Labs SDK family; no provenance is consistent across all versions of this package. | ai | |
| typosquat | typosquat.levenshtein:glob | AI (typosquat): Scoped @dynamic-labs/flow is a Flow blockchain connector, not a typosquat of glob; Levenshtein match is coincidental. | ai |
Versions (showing 51 of 204)
| Version | Deps | Published |
|---|---|---|
| 4.88.1 | 5 / 0 | |
| 4.88.0 | 5 / 0 | |
| 4.87.2 | 5 / 0 | |
| 4.87.1 | 5 / 0 | |
| 4.87.0 | 5 / 0 | |
| 4.86.0 | 5 / 0 | |
| 4.85.0 | 5 / 0 | |
| 4.84.1 | 5 / 0 | |
| 4.84.0 | 5 / 0 | |
| 4.83.1 | 5 / 0 | |
| 4.83.0 | 5 / 0 | |
| 4.82.0 | 5 / 0 | |
| 4.81.0 | 5 / 0 | |
| 4.80.0 | 5 / 0 | |
| 4.79.2 | 5 / 0 | |
| 4.79.1 | 5 / 0 | |
| 4.79.0 | 5 / 0 | |
| 4.78.1 | 5 / 0 | |
| 4.78.0 | 5 / 0 | |
| 4.77.4 | 5 / 0 | |
| 4.77.3 | 5 / 0 | |
| 4.77.2 | 5 / 0 | |
| 4.77.1 | 5 / 0 | |
| 4.77.0 | 5 / 0 | |
| 4.76.0 | 5 / 0 | |
| 4.75.0 | 5 / 0 | |
| 4.74.1 | 5 / 0 | |
| 4.74.0 | 5 / 0 | |
| 4.73.2 | 5 / 0 | |
| 4.73.0 | 5 / 0 | |
| 4.72.0 | 5 / 0 | |
| 4.71.0 | 5 / 0 | |
| 4.70.0 | 5 / 0 | |
| 4.69.0 | 5 / 0 | |
| 4.68.0 | 5 / 0 | |
| 4.67.2 | 5 / 0 | |
| 4.67.1 | 5 / 0 | |
| 4.67.0 | 5 / 0 | |
| 4.66.0 | 5 / 0 | |
| 4.65.0 | 5 / 0 | |
| 4.64.0 | 5 / 0 | |
| 4.63.1 | 5 / 0 | |
| 4.63.0 | 5 / 0 | |
| 4.62.0 | 5 / 0 | |
| 4.61.7 | 5 / 0 | |
| 4.61.6 | 5 / 0 | |
| 4.61.5 | 5 / 0 | |
| 4.61.4 | 5 / 0 | |
| 4.61.3 | 5 / 0 | |
| 4.61.2 | 5 / 0 | |
| 4.61.1 | 5 / 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.77.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.77.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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. Consider requesting the maintainer enable provenance via CI/CD.
v4.74.1
1 findingPackage 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 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.71.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.70.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.69.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.68.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.67.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.67.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.67.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.66.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.65.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.64.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.63.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.63.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.62.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.61.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.61.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.61.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.