@0xsequence/sessions
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established 0xsequence monorepo; provenance absence is consistent across all versions and not a risk indicator here. | ai |
Versions (showing 51 of 94)
| Version | Deps | Published |
|---|---|---|
| 2.3.44 | 5 / 6 | |
| 2.3.43 | 5 / 6 | |
| 2.3.42 | 5 / 6 | |
| 2.3.41 | 5 / 6 | |
| 2.3.40 | 5 / 6 | |
| 2.3.39 | 5 / 6 | |
| 2.3.38 | 5 / 6 | |
| 2.3.37 | 5 / 6 | |
| 2.3.36 | 5 / 6 | |
| 2.3.35 | 5 / 6 | |
| 2.3.34 | 5 / 6 | |
| 2.3.33 | 5 / 6 | |
| 2.3.32 | 5 / 6 | |
| 2.3.31 | 5 / 6 | |
| 2.3.30 | 5 / 6 | |
| 2.3.29 | 5 / 6 | |
| 2.3.28 | 5 / 6 | |
| 2.3.27 | 5 / 6 | |
| 2.3.26 | 5 / 6 | |
| 2.3.25 | 5 / 6 | |
| 2.3.24 | 5 / 6 | |
| 2.3.23 | 5 / 6 | |
| 2.3.22 | 5 / 6 | |
| 2.3.20 | 5 / 6 | |
| 2.3.19 | 5 / 6 | |
| 2.3.18 | 5 / 6 | |
| 2.3.17 | 5 / 6 | |
| 2.3.14 | 5 / 6 | |
| 2.3.13 | 5 / 6 | |
| 2.3.12 | 5 / 6 | |
| 2.3.11 | 5 / 6 | |
| 2.3.10 | 5 / 6 | |
| 2.3.9 | 5 / 6 | |
| 2.3.8 | 5 / 6 | |
| 2.3.7 | 5 / 6 | |
| 2.3.6 | 5 / 6 | |
| 2.3.5 | 5 / 6 | |
| 2.3.4 | 5 / 6 | |
| 2.3.3 | 5 / 6 | |
| 2.3.2 | 5 / 6 | |
| 2.3.1 | 5 / 6 | |
| 2.3.0 | 5 / 6 | |
| 2.2.15 | 5 / 6 | |
| 2.2.14 | 5 / 6 | |
| 2.2.13 | 5 / 6 | |
| 2.2.12 | 5 / 6 | |
| 2.2.11 | 5 / 6 | |
| 2.2.10 | 5 / 6 | |
| 2.2.9 | 5 / 6 | |
| 2.2.8 | 5 / 6 | |
| 2.2.7 | 5 / 6 |
v2.3.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.10
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (taylanpince) than the most recent previously approved version (pkieltyka) on 2025-04-29, but taylanpince 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.
v2.3.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.8
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pkieltyka) than the most recent previously approved version (taylanpince) on 2025-04-08, but pkieltyka 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.
v2.3.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (taylanpince) than the most recent previously approved version (pkieltyka) on 2025-04-02, but taylanpince 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.
v2.3.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pkieltyka) than the most recent previously approved version (taylanpince) on 2025-03-27, but pkieltyka 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.
v2.3.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (pkieltyka) than the most recent previously approved version (taylanpince) on 2025-03-26, but pkieltyka 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.
v2.2.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.12
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.