@equos/browser-sdk
Equos browser sdk
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 |
|---|---|---|---|---|
| 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 address; domain hijacking rule does not apply. | ai | |
| phantom-deps | phantom-dep:@r2wc/react-to-web-component | AI (phantom-deps): Package is a declared runtime dependency used in the web component build; phantom-dep heuristic misfires here. | ai |
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 3.1.4 | 1 / 13 | |
| 3.1.3 | 1 / 13 | |
| 3.1.2 | 1 / 13 | |
| 3.0.4 | 1 / 13 | |
| 3.0.3 | 1 / 13 | |
| 3.0.2 | 1 / 13 | |
| 1.5.5 | 1 / 18 | |
| 1.5.4 | 1 / 18 | |
| 1.5.3 | 1 / 18 | |
| 1.5.2 | 1 / 18 | |
| 1.5.1 | 1 / 18 | |
| 1.5.0 | 1 / 18 | |
| 1.4.1 | 1 / 18 |
v3.1.4
2 findingsMaintainer 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
2 findingsMaintainer 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
2 findingsMaintainer 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.0.4
2 findingsMaintainer 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.0.3
2 findingsMaintainer 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.0.2
2 findingsMaintainer 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.
v1.5.5
2 findingsMaintainer 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.
v1.5.4
2 findingsMaintainer 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.
v1.5.3
2 findingsMaintainer 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.
v1.5.2
2 findingsMaintainer 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.
v1.5.1
2 findingsMaintainer 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.
v1.5.0
2 findingsMaintainer 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.
v1.4.1
2 findingsMaintainer 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.