@0xsequence/waas No license 51 versions

@0xsequence/waas

npm Repository Homepage

51

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

Versions (showing 51 of 81)

View all versions

Version	Deps	Published
2.3.44	6 / 3	2026-06-02
2.3.43	6 / 3	2026-03-24
2.3.42	7 / 3	2026-03-23
2.3.41	7 / 3	2026-02-16
2.3.40	7 / 3	2026-02-06
2.3.39	7 / 3	2025-12-15
2.3.38	7 / 3	2025-12-04
2.3.37	7 / 3	2025-12-02
2.3.36	7 / 3	2025-12-01
2.3.35	7 / 3	2025-11-19
2.3.34	7 / 3	2025-11-17
2.3.19	7 / 3	2025-06-16
2.3.18	7 / 3	2025-06-16
2.3.17	7 / 3	2025-05-26
2.3.14	7 / 3	2025-05-21
2.3.13	7 / 3	2025-05-20
2.3.12	7 / 3	2025-05-07
2.3.11	7 / 3	2025-05-01
2.3.10	7 / 3	2025-04-29
2.3.9	7 / 3	2025-04-15
2.3.8	7 / 3	2025-04-08
2.3.7	7 / 3	2025-04-03
2.3.6	7 / 3	2025-04-02
2.3.5	7 / 3	2025-04-02
2.3.4	7 / 3	2025-03-29
2.3.3	7 / 3	2025-03-29
2.3.2	7 / 3	2025-03-28
2.3.1	7 / 3	2025-03-27
2.3.0	7 / 3	2025-03-26
2.2.15	7 / 3	2025-03-17
2.2.14	7 / 3	2025-02-26
2.2.13	7 / 3	2025-02-11
2.2.12	7 / 3	2025-02-10
2.2.11	7 / 3	2025-02-05
2.2.10	7 / 3	2025-02-03
2.2.9	7 / 3	2025-01-30
2.2.8	7 / 3	2025-01-22
2.2.7	7 / 3	2025-01-15
2.2.6	7 / 3	2025-01-14
2.2.5	7 / 3	2025-01-10
2.2.4	7 / 3	2025-01-08
2.2.3	7 / 3	2024-12-17
2.2.2	7 / 3	2024-12-14
2.2.1	7 / 3	2024-12-12
2.2.0	7 / 3	2024-12-11
2.1.8	7 / 3	2024-12-09
2.1.7	7 / 3	2024-12-06
2.1.6	7 / 3	2024-12-04
2.1.5	7 / 3	2024-12-03
2.1.4	7 / 3	2024-12-03
2.1.3	7 / 3	2024-11-29

v2.3.11

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-05-01, known maintainer) provenance

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

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-15, known maintainer) provenance

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

1 finding

LOW No provenance attestation provenance

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

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

1 finding

LOW No provenance attestation provenance

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

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.