@harness-engineering/core
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:cors | AI (typosquat): Scoped monorepo package; 'core' suffix in a scoped namespace is not a typosquat of 'cors'. | ai | |
| phantom-deps | phantom-dep:tree-sitter-wasms | AI (phantom-deps): Platform-specific binary package; phantom-dep heuristic doesn't apply to binary deps. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 0.28.0 | 11 / 7 | |
| 0.27.0 | 11 / 7 | |
| 0.26.4 | 11 / 7 | |
| 0.26.3 | 11 / 7 | |
| 0.26.2 | 11 / 7 | |
| 0.26.1 | 11 / 7 | |
| 0.26.0 | 11 / 7 | |
| 0.25.0 | 11 / 7 | |
| 0.24.0 | 11 / 7 | |
| 0.23.8 | 10 / 7 | |
| 0.23.7 | 10 / 7 | |
| 0.23.6 | 9 / 7 | |
| 0.23.5 | 9 / 7 | |
| 0.23.4 | 9 / 7 | |
| 0.23.3 | 9 / 7 | |
| 0.23.2 | 9 / 7 | |
| 0.23.1 | 9 / 7 | |
| 0.23.0 | 9 / 7 | |
| 0.22.0 | 9 / 7 | |
| 0.21.4 | 9 / 7 | |
| 0.21.3 | 9 / 7 | |
| 0.21.2 | 9 / 7 | |
| 0.21.1 | 9 / 7 | |
| 0.21.0 | 9 / 7 | |
| 0.20.0 | 9 / 7 | |
| 0.19.0 | 9 / 7 | |
| 0.18.0 | 9 / 7 | |
| 0.17.1 | 9 / 7 | |
| 0.17.0 | 9 / 7 | |
| 0.16.0 | 9 / 7 | |
| 0.15.0 | 9 / 7 | |
| 0.14.0 | 7 / 7 | |
| 0.13.1 | 7 / 7 | |
| 0.13.0 | 7 / 7 | |
| 0.12.0 | 7 / 7 | |
| 0.11.0 | 7 / 7 | |
| 0.10.1 | 5 / 6 | |
| 0.10.0 | 5 / 6 | |
| 0.9.2 | 5 / 6 | |
| 0.9.1 | 5 / 6 | |
| 0.9.0 | 5 / 6 | |
| 0.8.0 | 5 / 5 | |
| 0.7.0 | 5 / 5 | |
| 0.6.0 | 5 / 5 | |
| 0.5.0 | 5 / 5 |
v0.28.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.27.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.4
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.3
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.2
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.1
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.26.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.25.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.8
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.7
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.6
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.5
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.4
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.2
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.23.1
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.22.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.4
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.3
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.2
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.1
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.21.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.20.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.18.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.1
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.16.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.15.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.1
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.12.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.11.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.1
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.2
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.1
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.8.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.7.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.0
2 findingsPackage name '@harness-engineering/core' is 1 edit(s) away from popular package 'cors'.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.