@onflow/fcl-core
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:@babel/runtime | AI (phantom-deps): Framework-scoped transitive dep; not directly imported by convention, stable FP for this package. | ai | |
| phantom-deps | phantom-dep:@onflow/util-uid | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable FP for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@onflow/interaction | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic is a stable FP for this monorepo package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.30.2 | 18 / 10 | |
| 1.30.1 | 18 / 10 | |
| 1.30.0 | 18 / 10 | |
| 1.29.0 | 18 / 10 | |
| 1.23.1 | 18 / 10 | |
| 1.23.0 | 18 / 10 | |
| 1.22.3 | 18 / 10 | |
| 1.22.2 | 18 / 10 | |
| 1.22.1 | 18 / 10 | |
| 1.22.0 | 18 / 10 | |
| 1.21.2 | 18 / 10 | |
| 1.21.1 | 18 / 10 | |
| 1.21.0 | 18 / 10 | |
| 1.20.0 | 17 / 10 | |
| 1.19.0 | 17 / 10 | |
| 1.18.0 | 17 / 10 |
v1.30.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.30.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.30.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.29.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.23.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.22.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.