← Home

edge-paths

npm Repository

Get the paths of edge browser easily

16
Versions
MIT
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

shirshak

Keywords

browseredgepathsedge-pathsexistspath

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/main.js AI (source-diff): dist/main.js is standard TypeScript compiler output (tsc), not obfuscated code. Readable, benign Edge browser path resolution logic. ai
source-diff source-size-tripled AI (source-diff): Size increase from migrating to self-contained implementation (removing karma-edge-launcher dep). Expected for v1→v2 rewrite. ai
provenance missing-githead AI (provenance): Same long-time publisher, no code changes; gitHead absence reflects publish-env change, not a security concern. ai
phantom-deps phantom-dep:@types/which AI (phantom-deps): @types/which is the TS type declaration for the 'which' runtime dep; standard pattern for TypeScript packages. ai

Versions (showing 16 of 16)

Version Deps Published
3.0.5 2 / 3
3.0.4 2 / 3
3.0.3 2 / 3
3.0.2 2 / 3
3.0.1 2 / 3
3.0.0 2 / 3
2.2.1 2 / 2
2.2.0 1 / 3
2.1.0 0 / 3
2.0.0 0 / 3
1.0.5 1 / 0
1.0.4 1 / 0
1.0.3 1 / 0
1.0.2 1 / 0
1.0.1 1 / 0
1.0.0 1 / 0

v3.0.5

2 findings
HIGH Missing gitHead — previous versions had it provenance

This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: shirshak.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v3.0.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.2.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v2.0.0

2 findings
HIGH New obfuscated file: dist/main.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.