@onflow/transport-http
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:ws | AI (phantom-deps): ws is a transitive dep via isomorphic-ws; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped runtime; loaded by convention in Flow SDK ecosystem. | ai | |
| phantom-deps | phantom-dep:@onflow/util-template | AI (phantom-deps): Same-org scoped package; stable dependency pattern for Flow SDK. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 1.15.6 | 11 / 7 | |
| 1.15.5 | 11 / 7 | |
| 1.15.4 | 11 / 7 | |
| 1.15.1 | 11 / 7 | |
| 1.15.0 | 11 / 7 | |
| 1.14.0 | 11 / 7 | |
| 1.13.2 | 11 / 7 | |
| 1.13.1 | 11 / 7 | |
| 1.13.0 | 11 / 7 | |
| 1.10.0 | 10 / 5 |
v1.15.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.15.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.