@agent-scope/core
Core types, schemas, and serialization for Scope — zero dependencies
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
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 package @agent-scope/core; the name reflects its namespace, not a typosquat of 'cors'. | ai |
Versions (showing 51 of 64)
| Version | Deps | Published |
|---|---|---|
| 1.25.3 | 0 / 2 | |
| 1.25.2 | 0 / 2 | |
| 1.25.1 | 0 / 2 | |
| 1.25.0 | 0 / 2 | |
| 1.24.0 | 0 / 2 | |
| 1.23.0 | 0 / 2 | |
| 1.22.0 | 0 / 2 | |
| 1.21.11 | 0 / 2 | |
| 1.21.10 | 0 / 2 | |
| 1.21.9 | 0 / 2 | |
| 1.21.8 | 0 / 2 | |
| 1.21.7 | 0 / 2 | |
| 1.21.6 | 0 / 2 | |
| 1.21.5 | 0 / 2 | |
| 1.21.4 | 0 / 2 | |
| 1.21.3 | 0 / 2 | |
| 1.21.2 | 0 / 2 | |
| 1.21.1 | 0 / 2 | |
| 1.21.0 | 0 / 2 | |
| 1.20.19 | 0 / 2 | |
| 1.20.18 | 0 / 2 | |
| 1.20.17 | 0 / 2 | |
| 1.20.16 | 0 / 2 | |
| 1.20.15 | 0 / 2 | |
| 1.20.14 | 0 / 2 | |
| 1.20.13 | 0 / 2 | |
| 1.20.12 | 0 / 2 | |
| 1.20.11 | 0 / 2 | |
| 1.20.10 | 0 / 2 | |
| 1.20.9 | 0 / 2 | |
| 1.20.8 | 0 / 2 | |
| 1.20.7 | 0 / 2 | |
| 1.20.6 | 0 / 2 | |
| 1.20.5 | 0 / 2 | |
| 1.20.4 | 0 / 2 | |
| 1.20.3 | 0 / 2 | |
| 1.20.2 | 0 / 2 | |
| 1.20.1 | 0 / 2 | |
| 1.20.0 | 0 / 2 | |
| 1.19.0 | 0 / 2 | |
| 1.18.1 | 0 / 2 | |
| 1.18.0 | 0 / 2 | |
| 1.17.3 | 0 / 2 | |
| 1.17.2 | 0 / 2 | |
| 1.17.1 | 0 / 2 | |
| 1.17.0 | 0 / 2 | |
| 1.16.0 | 0 / 2 | |
| 1.15.0 | 0 / 2 | |
| 1.14.0 | 0 / 2 | |
| 1.13.0 | 0 / 2 | |
| 1.12.0 | 0 / 2 |
v1.25.3
2 findingsPackage name '@agent-scope/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.
v1.25.2
2 findingsPackage name '@agent-scope/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.
v1.25.1
2 findingsPackage name '@agent-scope/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.
v1.25.0
2 findingsPackage name '@agent-scope/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.
v1.24.0
2 findingsPackage name '@agent-scope/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.
v1.23.0
2 findingsPackage name '@agent-scope/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.
v1.22.0
2 findingsPackage name '@agent-scope/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.
v1.21.11
2 findingsPackage name '@agent-scope/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.
v1.21.10
2 findingsPackage name '@agent-scope/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.
v1.21.9
2 findingsPackage name '@agent-scope/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.
v1.21.8
2 findingsPackage name '@agent-scope/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.
v1.21.7
2 findingsPackage name '@agent-scope/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.
v1.21.6
2 findingsPackage name '@agent-scope/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.
v1.21.5
2 findingsPackage name '@agent-scope/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.
v1.21.4
2 findingsPackage name '@agent-scope/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.
v1.21.3
2 findingsPackage name '@agent-scope/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.
v1.21.2
2 findingsPackage name '@agent-scope/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.
v1.21.1
2 findingsPackage name '@agent-scope/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.
v1.21.0
2 findingsPackage name '@agent-scope/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.
v1.20.19
2 findingsPackage name '@agent-scope/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.
v1.20.18
2 findingsPackage name '@agent-scope/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.
v1.20.17
2 findingsPackage name '@agent-scope/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.
v1.20.16
2 findingsPackage name '@agent-scope/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.
v1.20.15
2 findingsPackage name '@agent-scope/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.
v1.20.14
2 findingsPackage name '@agent-scope/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.
v1.20.13
2 findingsPackage name '@agent-scope/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.
v1.20.12
2 findingsPackage name '@agent-scope/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.
v1.20.11
2 findingsPackage name '@agent-scope/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.
v1.20.10
2 findingsPackage name '@agent-scope/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.
v1.20.9
2 findingsPackage name '@agent-scope/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.
v1.20.8
2 findingsPackage name '@agent-scope/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.
v1.20.7
2 findingsPackage name '@agent-scope/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.
v1.20.6
2 findingsPackage name '@agent-scope/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.
v1.20.5
2 findingsPackage name '@agent-scope/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.
v1.20.4
2 findingsPackage name '@agent-scope/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.
v1.20.3
2 findingsPackage name '@agent-scope/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.
v1.20.2
2 findingsPackage name '@agent-scope/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.
v1.20.1
2 findingsPackage name '@agent-scope/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.
v1.20.0
2 findingsPackage name '@agent-scope/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.
v1.19.0
2 findingsPackage name '@agent-scope/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.
v1.18.1
2 findingsPackage name '@agent-scope/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.
v1.18.0
2 findingsPackage name '@agent-scope/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.
v1.17.3
2 findingsPackage name '@agent-scope/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.
v1.17.2
2 findingsPackage name '@agent-scope/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.
v1.17.1
2 findingsPackage name '@agent-scope/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.
v1.17.0
2 findingsPackage name '@agent-scope/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.
v1.16.0
2 findingsPackage name '@agent-scope/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.
v1.15.0
2 findingsPackage name '@agent-scope/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.
v1.14.0
2 findingsPackage name '@agent-scope/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.
v1.13.0
2 findingsPackage name '@agent-scope/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.
v1.12.0
2 findingsPackage name '@agent-scope/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.