@heliosjs/http
Http server support for @heliosjs
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 |
|---|---|---|---|---|
| source-diff | source-size-dropped | AI (source-diff): Legitimate size reduction from removing build/test artifacts; SLSA provenance confirms integrity. | ai | |
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): GraphQL library; dependencies referenced in type definitions and configs, not direct imports. | ai | |
| phantom-deps | phantom-dep:graphql-scalars | AI (phantom-deps): GraphQL library; dependencies referenced in type definitions and configs, not direct imports. | ai | |
| dependencies | unvetted-dep:type-graphql | AI (dependencies): type-graphql is a well-known, widely-used GraphQL library; no malicious indicators for this package's use case. | ai |
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 9.0.9 | 1 / 0 | |
| 9.0.8 | 1 / 0 | |
| 9.0.7 | 1 / 0 | |
| 9.0.6 | 1 / 0 | |
| 9.0.5 | 1 / 0 | |
| 9.0.4 | 1 / 0 | |
| 9.0.1 | 1 / 0 | |
| 7.0.10 | 1 / 0 | |
| 7.0.9 | 1 / 0 | |
| 7.0.8 | 1 / 0 | |
| 7.0.6 | 1 / 0 | |
| 5.0.0 | 1 / 0 | |
| 4.0.0 | 6 / 0 | |
| 3.0.0 | 6 / 0 | |
| 2.0.0 | 6 / 0 | |
| 1.3.3 | 6 / 0 | |
| 1.2.1 | 6 / 0 | |
| 1.0.8 | 6 / 0 | |
| 1.0.6 | 6 / 0 | |
| 1.0.5 | 6 / 0 | |
| 1.0.3 | 6 / 0 |
v9.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v9.0.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v4.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.0.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.