@dynamic-labs/midnight
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 |
|---|---|---|---|---|
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Dynamic Labs org routinely publishes 0.0.0 placeholder packages to reserve namespaces. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Namespace placeholder from established publisher; sparse metadata is intentional. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Intentional placeholder; no description expected for namespace reservation. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Growth reflects addition of first-party @dynamic-labs sibling packages at matching version; expected for monorepo expansion. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase directly attributable to three new first-party runtime deps bundled at same release version. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 4.88.1 | 7 / 0 | |
| 4.88.0 | 7 / 0 | |
| 4.87.2 | 7 / 0 | |
| 4.87.1 | 7 / 0 | |
| 4.87.0 | 7 / 0 | |
| 4.86.0 | 7 / 0 | |
| 4.85.0 | 7 / 0 | |
| 4.84.1 | 7 / 0 | |
| 4.84.0 | 7 / 0 | |
| 4.83.1 | 7 / 0 | |
| 4.83.0 | 7 / 0 | |
| 4.82.0 | 7 / 0 | |
| 4.81.0 | 7 / 0 | |
| 4.80.0 | 7 / 0 | |
| 4.79.2 | 6 / 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 | 2 / 0 | |
| 4.77.2 | 2 / 0 | |
| 4.77.1 | 2 / 0 | |
| 4.77.0 | 2 / 0 | |
| 4.76.0 | 1 / 0 | |
| 4.75.0 | 1 / 0 | |
| 0.0.0 | 0 / 0 |
v4.88.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.88.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.87.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.86.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.85.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.84.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.84.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.83.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.83.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.82.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.81.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.80.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.79.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.79.1
1 findingPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.78.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.77.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.77.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.77.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.77.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.77.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.76.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.75.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.