@heliosjs/core
Core functionality 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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:url | AI (phantom-deps): url is a Node.js polyfill; commonly declared but used indirectly via transpilation. | ai | |
| phantom-deps | phantom-dep:tsconfig-paths | AI (phantom-deps): tsconfig-paths is a config-only utility; not imported in code. Stable pattern for this package. | ai | |
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped package @heliosjs/core; 'core' vs 'cors' is incidental, not impersonation of the cors package. | ai | |
| dependencies | unvetted-dep:http | AI (dependencies): [email protected] is npm's security placeholder; no malicious code, just a misguided dep on a built-in module name. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 3.1.11 | 7 / 0 | |
| 3.1.10 | 7 / 0 | |
| 3.1.9 | 7 / 0 | |
| 3.1.7 | 7 / 0 | |
| 3.1.6 | 7 / 0 | |
| 3.1.4 | 7 / 0 | |
| 2.4.10 | 7 / 0 | |
| 2.4.9 | 7 / 0 | |
| 2.4.8 | 7 / 0 | |
| 2.1.4 | 9 / 1 | |
| 2.0.0 | 9 / 1 | |
| 1.4.1 | 9 / 1 | |
| 1.3.6 | 10 / 1 | |
| 1.0.3 | 10 / 0 | |
| 1.0.2 | 8 / 0 |
v3.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v2.4.9
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.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.3.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.