← Home

fingerprint-injector

npm Repository Homepage
28
Versions
—
License
No
Install Scripts
Attested
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation (unverified) npm registry signatures No source commit

Maintainers

mtrunkatjancurnpetrpatekmnmkngjaroslavhejlekdrobnikjmetalwarrior665fnesvedab4nanjanbucharapify-service-account

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance missing-githead AI (provenance): CI-published with SLSA attestation; gitHead omission is metadata noise, not a provenance regression. ai
semgrep semgrep:api-obfuscation-reflect AI (semgrep): Reflect.get() is the intended proxy mechanism for browser fingerprint injection; not malicious obfuscation. ai
dependencies unvetted-dep:fingerprint-generator AI (dependencies): Sibling package in the same Apify monorepo, published at matching version; stable false positive. ai

Versions (showing 28 of 28)

Version Deps Published
2.1.86 2 / 0
2.1.82 2 / 0
2.1.81 2 / 0
2.1.80 2 / 0
2.1.79 2 / 0
2.1.78 2 / 0
2.1.77 2 / 0
2.1.76 2 / 0
2.1.75 2 / 0
2.1.74 2 / 0
2.1.73 2 / 0
2.1.72 2 / 0
2.1.70 2 / 0
2.1.69 2 / 0
2.1.68 2 / 0
2.1.67 2 / 0
2.1.66 2 / 0
2.1.65 2 / 0
2.1.64 2 / 0
2.1.63 2 / 0
2.1.62 2 / 0
2.1.61 2 / 0
2.1.60 2 / 0
2.1.57 2 / 0
2.1.56 2 / 0
2.1.55 2 / 0
2.1.54 2 / 0
2.1.52 2 / 0

v2.1.86

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: GitHub Actions.

INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v2.1.66

1 finding
LOW No provenance attestation provenance

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

v2.1.65

1 finding
LOW No provenance attestation provenance

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

v2.1.64

1 finding
LOW No provenance attestation provenance

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

v2.1.63

1 finding
LOW No provenance attestation provenance

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

v2.1.62

1 finding
LOW No provenance attestation provenance

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

v2.1.61

1 finding
LOW No provenance attestation provenance

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

v2.1.60

1 finding
LOW No provenance attestation provenance

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

v2.1.57

1 finding
LOW No provenance attestation provenance

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

v2.1.56

1 finding
LOW No provenance attestation provenance

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

v2.1.55

1 finding
LOW No provenance attestation provenance

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

v2.1.54

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v2.1.52

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.