@0xsequence/network
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 |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-tlds | AI (semgrep): Fires on blockchain explorer URLs in constants.ts; legitimate network configuration, not C2/exfiltration. | ai |
Versions (showing 51 of 81)
| Version | Deps | Published |
|---|---|---|
| 2.3.44 | 4 / 1 | |
| 2.3.43 | 4 / 1 | |
| 2.3.42 | 4 / 1 | |
| 2.3.41 | 4 / 1 | |
| 2.3.40 | 4 / 1 | |
| 2.3.39 | 4 / 1 | |
| 2.3.38 | 4 / 1 | |
| 2.3.37 | 4 / 1 | |
| 2.3.36 | 4 / 1 | |
| 2.3.35 | 4 / 1 | |
| 2.3.34 | 4 / 1 | |
| 2.3.19 | 4 / 1 | |
| 2.3.18 | 4 / 1 | |
| 2.3.17 | 4 / 1 | |
| 2.3.14 | 4 / 1 | |
| 2.3.13 | 4 / 1 | |
| 2.3.12 | 4 / 1 | |
| 2.3.11 | 4 / 1 | |
| 2.3.10 | 4 / 1 | |
| 2.3.9 | 4 / 1 | |
| 2.3.8 | 4 / 1 | |
| 2.3.7 | 4 / 1 | |
| 2.3.6 | 4 / 1 | |
| 2.3.5 | 4 / 1 | |
| 2.3.4 | 4 / 1 | |
| 2.3.3 | 4 / 1 | |
| 2.3.2 | 4 / 1 | |
| 2.3.1 | 4 / 1 | |
| 2.3.0 | 4 / 1 | |
| 2.2.15 | 4 / 1 | |
| 2.2.14 | 4 / 1 | |
| 2.2.13 | 4 / 1 | |
| 2.2.12 | 4 / 1 | |
| 2.2.11 | 4 / 1 | |
| 2.2.10 | 4 / 1 | |
| 2.2.9 | 4 / 1 | |
| 2.2.8 | 4 / 1 | |
| 2.2.7 | 4 / 1 | |
| 2.2.6 | 4 / 1 | |
| 2.2.5 | 4 / 1 | |
| 2.2.4 | 4 / 1 | |
| 2.2.3 | 4 / 1 | |
| 2.2.2 | 4 / 1 | |
| 2.2.1 | 4 / 1 | |
| 2.2.0 | 4 / 1 | |
| 2.1.8 | 4 / 1 | |
| 2.1.7 | 4 / 1 | |
| 2.1.6 | 4 / 1 | |
| 2.1.5 | 4 / 1 | |
| 2.1.4 | 4 / 1 | |
| 2.1.3 | 4 / 1 |
v2.3.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.8
2 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.5
2 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
2 findingsPackage 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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.7
2 findingsPackage 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 (naivesheep) on 2025-01-15, 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.2.6
2 findingsPackage 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 (naivesheep) on 2025-01-14, 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.2.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.3
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (naivesheep) than the most recent previously approved version (pkieltyka) on 2024-12-17, but naivesheep 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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.1
2 findingsPackage 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 (naivesheep) on 2024-12-12, 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.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (naivesheep) than the most recent previously approved version (taylanpince) on 2024-12-11, but naivesheep 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.1.8
2 findingsPackage 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 (naivesheep) on 2024-12-09, 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.1.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (naivesheep) than the most recent previously approved version (taylanpince) on 2024-12-06, but naivesheep 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.1.6
2 findingsPackage 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 (naivesheep) on 2024-12-04, 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.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.4
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (naivesheep) than the most recent previously approved version (pkieltyka) on 2024-12-03, but naivesheep 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.1.3
2 findingsPackage 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 (naivesheep) on 2024-11-29, 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.