← Home

@0xsequence/provider

npm Repository Homepage
97
Versions
—
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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

naivesheeppkieltykaagusx1211taylanpincemilkytaste

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:@0xsequence/wallet AI (phantom-deps): Same-org sibling dep; may be re-exported or used indirectly in monorepo. ai
phantom-deps phantom-dep:@0xsequence/relayer AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo package. ai
phantom-deps phantom-dep:@0xsequence/migration AI (phantom-deps): Same-org sibling dep; stable false positive for this monorepo package. ai
bogus-package bogus-package AI (bogus-package): Established monorepo sub-package; sparse README and no keywords are consistent across all 0xsequence packages. ai

Versions (showing 97 of 97)

Version Deps Published
2.3.44 12 / 3
2.3.43 12 / 3
2.3.42 12 / 3
2.3.41 12 / 3
2.3.40 12 / 3
2.3.39 12 / 3
2.3.38 12 / 3
2.3.37 12 / 3
2.3.36 12 / 3
2.3.35 12 / 3
2.3.34 12 / 3
2.3.33 12 / 3
2.3.32 12 / 3
2.3.31 12 / 3
2.3.30 12 / 3
2.3.29 12 / 3
2.3.28 12 / 3
2.3.27 12 / 3
2.3.26 12 / 3
2.3.25 12 / 3
2.3.24 12 / 3
2.3.23 12 / 3
2.3.22 12 / 3
2.3.21 12 / 3
2.3.20 12 / 3
2.3.19 12 / 3
2.3.18 12 / 3
2.3.17 12 / 3
2.3.16 12 / 3
2.3.15 12 / 3
2.3.14 12 / 3
2.3.13 12 / 3
2.3.12 12 / 3
2.3.11 12 / 3
2.3.10 12 / 3
2.3.9 12 / 3
2.3.8 12 / 3
2.3.7 12 / 3
2.3.6 12 / 3
2.3.5 12 / 3
2.3.4 12 / 3
2.3.3 12 / 3
2.3.2 12 / 3
2.3.1 12 / 3
2.3.0 12 / 3
2.2.15 12 / 3
2.2.14 12 / 3
2.2.13 12 / 3
2.2.12 12 / 3
2.2.11 12 / 3
2.2.10 12 / 3
2.2.9 12 / 3
2.2.8 12 / 3
2.2.7 12 / 3
2.2.6 12 / 3
2.2.5 12 / 3
2.2.4 12 / 3
2.2.3 12 / 3
2.2.2 12 / 3
2.2.1 12 / 3
2.2.0 12 / 3
2.1.8 12 / 3
2.1.7 12 / 3
2.1.6 12 / 3
2.1.5 12 / 3
2.1.4 12 / 3
2.1.3 12 / 3
2.1.2 12 / 3
2.1.1 12 / 3
2.1.0 12 / 3
2.0.26 12 / 3
2.0.25 12 / 3
2.0.24 12 / 3
2.0.23 12 / 3
2.0.22 12 / 3
2.0.21 12 / 3
2.0.20 12 / 3
2.0.19 12 / 3
2.0.18 12 / 3
2.0.17 12 / 3
2.0.16 12 / 3
2.0.15 12 / 3
2.0.14 12 / 3
2.0.13 12 / 3
2.0.12 12 / 3
2.0.11 12 / 3
2.0.10 12 / 3
2.0.9 12 / 3
2.0.8 12 / 3
2.0.7 12 / 3
2.0.6 12 / 3
2.0.5 12 / 3
2.0.4 12 / 3
2.0.3 12 / 3
2.0.2 12 / 3
2.0.1 12 / 3
2.0.0 12 / 3

v2.3.11

1 finding
LOW No provenance attestation provenance

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

v2.3.10

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: pkieltyka → taylanpince (on 2025-04-29, known maintainer) provenance

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
LOW No provenance attestation provenance

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

v2.3.8

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: taylanpince → pkieltyka (on 2025-04-08, known maintainer) provenance

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
LOW No provenance attestation provenance

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

v2.3.6

1 finding
LOW No provenance attestation provenance

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

v2.3.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: pkieltyka → taylanpince (on 2025-04-02, known maintainer) provenance

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
LOW No provenance attestation provenance

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

v2.3.3

1 finding
LOW No provenance attestation provenance

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

v2.3.2

1 finding
LOW No provenance attestation provenance

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

v2.3.1

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: taylanpince → pkieltyka (on 2025-03-27, known maintainer) provenance

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
LOW No provenance attestation provenance

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

INFO Publisher changed: taylanpince → pkieltyka (on 2025-03-26, known maintainer) provenance

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
LOW No provenance attestation provenance

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

v2.2.14

1 finding
LOW No provenance attestation provenance

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

v2.2.13

1 finding
LOW No provenance attestation provenance

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

v2.2.12

1 finding
LOW No provenance attestation provenance

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

v2.2.11

1 finding
LOW No provenance attestation provenance

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

v2.2.10

1 finding
LOW No provenance attestation provenance

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

v2.2.9

1 finding
LOW No provenance attestation provenance

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

v2.2.8

1 finding
LOW No provenance attestation provenance

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

v2.2.7

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: naivesheep → taylanpince (on 2025-01-15, known maintainer) provenance

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 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: naivesheep → taylanpince (on 2025-01-14, known maintainer) provenance

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 finding
LOW No provenance attestation provenance

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

v2.2.4

1 finding
LOW No provenance attestation provenance

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

v2.2.3

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: pkieltyka → naivesheep (on 2024-12-17, known maintainer) provenance

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 finding
LOW No provenance attestation provenance

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

v2.2.1

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: naivesheep → pkieltyka (on 2024-12-12, known maintainer) provenance

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 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: taylanpince → naivesheep (on 2024-12-11, known maintainer) provenance

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 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: naivesheep → taylanpince (on 2024-12-09, known maintainer) provenance

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 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: taylanpince → naivesheep (on 2024-12-06, known maintainer) provenance

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 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: naivesheep → taylanpince (on 2024-12-04, known maintainer) provenance

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 finding
LOW No provenance attestation provenance

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

v2.1.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: pkieltyka → naivesheep (on 2024-12-03, known maintainer) provenance

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 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: naivesheep → pkieltyka (on 2024-11-29, known maintainer) provenance

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.

v2.1.2

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: taylanpince → naivesheep (on 2024-11-27, known maintainer) provenance

This version was published by a different npm account (naivesheep) than the most recent previously approved version (taylanpince) on 2024-11-27, 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.1

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: naivesheep → taylanpince (on 2024-11-27, known maintainer) provenance

This version was published by a different npm account (taylanpince) than the most recent previously approved version (naivesheep) on 2024-11-27, 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.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.26

1 finding
LOW No provenance attestation provenance

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

v2.0.25

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: taylanpince → naivesheep (on 2024-11-07, known maintainer) provenance

This version was published by a different npm account (naivesheep) than the most recent previously approved version (taylanpince) on 2024-11-07, 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.0.24

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: taylanpince → naivesheep (on 2024-11-07, known maintainer) provenance

This version was published by a different npm account (naivesheep) than the most recent previously approved version (taylanpince) on 2024-11-07, 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.0.23

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: naivesheep → taylanpince (on 2024-11-06, known maintainer) provenance

This version was published by a different npm account (taylanpince) than the most recent previously approved version (naivesheep) on 2024-11-06, 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.0.22

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: naivesheep → taylanpince (on 2024-10-31, known maintainer) provenance

This version was published by a different npm account (taylanpince) than the most recent previously approved version (naivesheep) on 2024-10-31, 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.0.21

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: taylanpince → naivesheep (on 2024-10-24, known maintainer) provenance

This version was published by a different npm account (naivesheep) than the most recent previously approved version (taylanpince) on 2024-10-24, 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.0.20

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: taylanpince → pkieltyka (on 2024-10-24, known maintainer) provenance

This version was published by a different npm account (pkieltyka) than the most recent previously approved version (taylanpince) on 2024-10-24, 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.0.19

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: pkieltyka → taylanpince (on 2024-10-24, known maintainer) provenance

This version was published by a different npm account (taylanpince) than the most recent previously approved version (pkieltyka) on 2024-10-24, 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.0.18

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: pkieltyka → naivesheep (on 2024-10-22, known maintainer) provenance

This version was published by a different npm account (naivesheep) than the most recent previously approved version (pkieltyka) on 2024-10-22, 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.0.17

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: taylanpince → pkieltyka (on 2024-10-17, known maintainer) provenance

This version was published by a different npm account (pkieltyka) than the most recent previously approved version (taylanpince) on 2024-10-17, 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.0.16

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: naivesheep → taylanpince (on 2024-10-17, known maintainer) provenance

This version was published by a different npm account (taylanpince) than the most recent previously approved version (naivesheep) on 2024-10-17, 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.0.15

1 finding
LOW No provenance attestation provenance

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

v2.0.14

1 finding
LOW No provenance attestation provenance

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

v2.0.13

1 finding
LOW No provenance attestation provenance

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

v2.0.12

1 finding
LOW No provenance attestation provenance

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

v2.0.11

1 finding
LOW No provenance attestation provenance

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

v2.0.10

1 finding
LOW No provenance attestation provenance

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

v2.0.9

1 finding
LOW No provenance attestation provenance

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

v2.0.8

1 finding
LOW No provenance attestation provenance

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

v2.0.7

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: naivesheep → pkieltyka (on 2024-09-18, known maintainer) provenance

This version was published by a different npm account (pkieltyka) than the most recent previously approved version (naivesheep) on 2024-09-18, 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.0.6

1 finding
LOW No provenance attestation provenance

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

v2.0.5

1 finding
LOW No provenance attestation provenance

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

v2.0.4

1 finding
LOW No provenance attestation provenance

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

v2.0.3

1 finding
LOW No provenance attestation provenance

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

v2.0.2

1 finding
LOW No provenance attestation provenance

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

v2.0.1

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

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.