@equos/core
Equos.ai core js library.
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
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 AI/WebRTC SDK with distinct purpose and GitHub org; not a typosquat of cors. | ai | |
| email-domain | unclaimed-email:https://www.linkedin.com/in/lo%c3%afc-combis-a211a813a/ | AI (email-domain): Author field contains a LinkedIn URL, not an email domain; no registerable domain risk. | ai | |
| phantom-deps | phantom-dep:axios | AI (phantom-deps): axios is a declared runtime dependency; phantom-dep heuristic misfires here. | ai |
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 3.1.11 | 1 / 10 | |
| 3.1.10 | 1 / 10 | |
| 3.1.9 | 1 / 10 | |
| 3.1.8 | 1 / 10 | |
| 3.1.7 | 1 / 10 | |
| 3.1.6 | 1 / 10 | |
| 3.1.5 | 1 / 10 | |
| 3.1.4 | 1 / 10 | |
| 3.1.3 | 1 / 10 | |
| 3.1.2 | 1 / 10 |
v3.1.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.7
3 findingsPackage name '@equos/core' is 1 edit(s) away from popular package 'cors'.
Maintainer email 'https://www.linkedin.com/in/lo%C3%AFc-combis-a211a813a/' uses domain 'https://www.linkedin.com/in/lo%c3%afc-combis-a211a813a/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.6
3 findingsPackage name '@equos/core' is 1 edit(s) away from popular package 'cors'.
Maintainer email 'https://www.linkedin.com/in/lo%C3%AFc-combis-a211a813a/' uses domain 'https://www.linkedin.com/in/lo%c3%afc-combis-a211a813a/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
3 findingsPackage name '@equos/core' is 1 edit(s) away from popular package 'cors'.
Maintainer email 'https://www.linkedin.com/in/lo%C3%AFc-combis-a211a813a/' uses domain 'https://www.linkedin.com/in/lo%c3%afc-combis-a211a813a/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
3 findingsPackage name '@equos/core' is 1 edit(s) away from popular package 'cors'.
Maintainer email 'https://www.linkedin.com/in/lo%C3%AFc-combis-a211a813a/' uses domain 'https://www.linkedin.com/in/lo%c3%afc-combis-a211a813a/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
3 findingsPackage name '@equos/core' is 1 edit(s) away from popular package 'cors'.
Maintainer email 'https://www.linkedin.com/in/lo%C3%AFc-combis-a211a813a/' uses domain 'https://www.linkedin.com/in/lo%c3%afc-combis-a211a813a/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
3 findingsPackage name '@equos/core' is 1 edit(s) away from popular package 'cors'.
Maintainer email 'https://www.linkedin.com/in/lo%C3%AFc-combis-a211a813a/' uses domain 'https://www.linkedin.com/in/lo%c3%afc-combis-a211a813a/' which has no DNS records. An attacker could register this domain to hijack the maintainer identity.
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.