← Home

@jitsu/js

npm Repository Homepage
20
Versions
—
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

priyankjitsujitsuhqvklmnabsorbb

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Package migrated to GitHub Actions CI publishing with SLSA attestation; legitimate supply chain improvement. ai
maintainer-change maintainer-added AI (maintainer-change): New maintainer added as part of org-level transition; consistent with GitHub Actions publishing migration. ai
typosquat typosquat.levenshtein:pg AI (typosquat): Same false positive pattern; unrelated to pg. ai
typosquat typosquat.levenshtein:rxjs AI (typosquat): Same false positive pattern; unrelated to rxjs. ai
typosquat typosquat.levenshtein:qs AI (typosquat): Scoped package @jitsu/js is the legitimate Jitsu analytics SDK; Levenshtein match to 'qs' is a false positive. ai
typosquat typosquat.levenshtein:ajv AI (typosquat): Same false positive pattern; unrelated to ajv. ai
typosquat typosquat.levenshtein:joi AI (typosquat): Same false positive pattern; unrelated to joi. ai
typosquat typosquat.levenshtein:jest AI (typosquat): Same false positive pattern; @jitsu/js is an established scoped package unrelated to jest. ai

Versions (showing 20 of 20)

Version Deps Published
1.11.0 1 / 19
1.10.4 1 / 25
1.10.3 1 / 25
1.10.2 1 / 25
1.10.1 1 / 25
1.10.0 1 / 24
1.9.17 1 / 25
1.9.15 1 / 25
1.9.14 1 / 25
1.9.13 1 / 25
1.9.12 1 / 25
1.9.11 1 / 25
1.9.10 1 / 25
1.9.9 1 / 25
1.9.8 1 / 25
1.9.7 1 / 25
1.9.6 1 / 24
1.9.5 1 / 24
1.9.4 1 / 24
1.9.3 1 / 24

v1.10.0

1 finding
LOW No provenance attestation provenance

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

v1.9.17

1 finding
LOW No provenance attestation provenance

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

v1.9.15

1 finding
LOW No provenance attestation provenance

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

v1.9.14

1 finding
LOW No provenance attestation provenance

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

v1.9.13

1 finding
LOW No provenance attestation provenance

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

v1.9.12

1 finding
LOW No provenance attestation provenance

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

v1.9.11

1 finding
LOW No provenance attestation provenance

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

v1.9.10

1 finding
LOW No provenance attestation provenance

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

v1.9.9

1 finding
LOW No provenance attestation provenance

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

v1.9.8

1 finding
LOW No provenance attestation provenance

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

v1.9.7

1 finding
LOW No provenance attestation provenance

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

v1.9.6

1 finding
LOW No provenance attestation provenance

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

v1.9.5

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vklmn → jitsuhq (on 2024-06-14, known maintainer) provenance

This version was published by a different npm account (jitsuhq) than the most recent previously approved version (vklmn) on 2024-06-14, but jitsuhq is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.9.4

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: vklmn → jitsuhq (on 2024-05-31, known maintainer) provenance

This version was published by a different npm account (jitsuhq) than the most recent previously approved version (vklmn) on 2024-05-31, but jitsuhq is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.9.3

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.