@agent-facets/core
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-facets/core; 'core' suffix in a scoped namespace is not a typosquat of 'cors'. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.9.1 | 5 / 0 | |
| 0.7.0 | 5 / 0 | |
| 0.6.5 | 5 / 0 | |
| 0.6.3 | 5 / 2 | |
| 0.6.2 | 4 / 5 | |
| 0.6.0 | 4 / 5 | |
| 0.5.1 | 4 / 5 | |
| 0.4.3 | 4 / 3 | |
| 0.4.2 | 4 / 3 | |
| 0.4.1 | 4 / 3 | |
| 0.4.0 | 4 / 3 | |
| 0.3.3 | 4 / 1 | |
| 0.3.2 | 4 / 1 | |
| 0.3.1 | 4 / 1 | |
| 0.3.0 | 4 / 1 | |
| 0.2.1 | 4 / 1 | |
| 0.2.0 | 4 / 1 | |
| 0.1.3 | 4 / 1 | |
| 0.1.2 | 3 / 1 | |
| 0.1.1 | 3 / 1 |
v0.9.1
2 findingsPackage name '@agent-facets/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.
v0.7.0
2 findingsPackage name '@agent-facets/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.
v0.6.5
2 findingsPackage name '@agent-facets/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.
v0.6.3
2 findingsPackage name '@agent-facets/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.
v0.6.2
2 findingsPackage name '@agent-facets/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.
v0.6.0
2 findingsPackage name '@agent-facets/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.
v0.5.1
2 findingsPackage name '@agent-facets/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.
v0.4.3
2 findingsPackage name '@agent-facets/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.
v0.4.2
2 findingsPackage name '@agent-facets/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.
v0.4.1
2 findingsPackage name '@agent-facets/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.
v0.4.0
2 findingsPackage name '@agent-facets/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.
v0.3.3
2 findingsPackage name '@agent-facets/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.
v0.3.2
2 findingsPackage name '@agent-facets/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.
v0.3.1
2 findingsPackage name '@agent-facets/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.
v0.3.0
2 findingsPackage name '@agent-facets/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.
v0.2.1
2 findingsPackage name '@agent-facets/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.
v0.2.0
2 findingsPackage name '@agent-facets/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.
v0.1.3
2 findingsPackage name '@agent-facets/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.
v0.1.2
2 findingsPackage name '@agent-facets/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.
v0.1.1
2 findingsPackage name '@agent-facets/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.