@onflow/fcl-wc
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:postcss-cli | AI (phantom-deps): Build-time CSS tooling; not a runtime import, stable pattern for this UI package. | ai | |
| phantom-deps | phantom-dep:tailwindcss | AI (phantom-deps): Build-time CSS framework; not a runtime import, stable pattern for this UI package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped runtime helpers loaded by convention; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@onflow/config | AI (phantom-deps): Same org scope; likely loaded indirectly via peer deps, stable false positive. | ai | |
| phantom-deps | phantom-dep:@walletconnect/types | AI (phantom-deps): Types-only package used in config/type declarations, not directly imported at runtime. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 6.0.22 | 11 / 9 | |
| 6.0.12 | 11 / 9 | |
| 6.0.11 | 11 / 9 | |
| 6.0.10 | 11 / 9 | |
| 6.0.9 | 11 / 9 | |
| 6.0.8 | 11 / 9 | |
| 6.0.7 | 11 / 9 | |
| 6.0.6 | 11 / 9 | |
| 6.0.5 | 11 / 9 | |
| 6.0.4 | 11 / 9 | |
| 6.0.3 | 11 / 9 | |
| 6.0.2 | 11 / 9 |
v6.0.22
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v6.0.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v6.0.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v6.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.