← Home

@0xsequence/connect

npm Repository
20
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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

naivesheeppkieltykaagusx1211taylanpincemilkytaste

Keywords

sequenceweb-sdkwallet

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/cjs/connectors/epic/EpicLogo.js AI (source-diff): Long lines are inline SVG path data in a CJS-compiled React component, not obfuscation. ai
phantom-deps phantom-dep:tailwindcss AI (phantom-deps): Build-time CSS tooling referenced in config scripts, not a runtime import; stable false positive for this package. ai
phantom-deps phantom-dep:@tailwindcss/cli AI (phantom-deps): Build-time CSS tooling referenced in config scripts, not a runtime import; stable false positive for this package. ai
phantom-deps phantom-dep:@0xsequence/utils AI (phantom-deps): Same-org transitive dep; used indirectly via other @0xsequence/* packages. ai
phantom-deps phantom-dep:@0xsequence/metadata AI (phantom-deps): Same-org transitive dep; used indirectly via other @0xsequence/* packages. ai

Versions (showing 20 of 20)

Version Deps Published
6.0.6 14 / 14
6.0.5 14 / 14
6.0.4 14 / 14
6.0.3 14 / 14
6.0.2 14 / 14
6.0.1 14 / 14
6.0.0 16 / 15
5.4.11 15 / 10
5.4.10 15 / 10
5.4.9 17 / 10
5.4.8 17 / 10
5.4.7 17 / 10
5.4.6 17 / 10
5.4.5 17 / 10
5.4.4 17 / 10
5.4.3 17 / 10
5.4.2 17 / 10
5.4.1 17 / 10
5.4.0 17 / 10
5.3.26 17 / 10

v6.0.6

1 finding
LOW No provenance attestation provenance

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

v6.0.5

1 finding
LOW No provenance attestation provenance

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

v6.0.4

1 finding
LOW No provenance attestation provenance

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

v6.0.3

1 finding
LOW No provenance attestation provenance

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

v6.0.2

1 finding
LOW No provenance attestation provenance

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

v6.0.1

1 finding
LOW No provenance attestation provenance

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

v6.0.0

1 finding
LOW No provenance attestation provenance

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

v5.4.11

2 findings
HIGH New obfuscated file: dist/cjs/connectors/epic/EpicLogo.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v5.4.10

2 findings
HIGH New obfuscated file: dist/cjs/connectors/epic/EpicLogo.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

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

v5.4.9

1 finding
LOW No provenance attestation provenance

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

v5.4.8

1 finding
LOW No provenance attestation provenance

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

v5.4.7

1 finding
LOW No provenance attestation provenance

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

v5.4.6

1 finding
LOW No provenance attestation provenance

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

v5.4.5

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.

v5.4.4

1 finding
LOW No provenance attestation provenance

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

v5.4.3

1 finding
LOW No provenance attestation provenance

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

v5.4.2

1 finding
LOW No provenance attestation provenance

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

v5.4.1

1 finding
LOW No provenance attestation provenance

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

v5.4.0

1 finding
LOW No provenance attestation provenance

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

v5.3.26

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.