@yamato-daiwa/es-extensions-browserjs MIT 28 versions

@yamato-daiwa/es-extensions-browserjs

npm Repository Homepage

Additional to @yamato-daiwa/es-extensions functionality for browser environment. Helper functions and classes aimed to reduce the routine code. Build-in TypeScript type safety.

28

Versions

MIT

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

yd-tokugawa_t

Keywords

typescriptutilsbrowserlogger

Versions (showing 28 of 28)

Version	Deps	Published
1.9.1	0 / 9	2026-07-08
1.9.0	0 / 9	2026-07-07
1.8.9	0 / 9	2026-07-08
1.8.8	0 / 9	2026-07-06
1.8.7	0 / 9	2026-03-21
1.8.6	0 / 9	2026-03-20
1.8.5	0 / 9	2026-02-09
1.8.4	0 / 9	2025-11-29
1.8.3	0 / 9	2025-11-29
1.8.2	0 / 9	2025-10-25
1.8.1	0 / 10	2025-09-22
1.8.0	0 / 10	2025-09-13
1.7.0	0 / 11	2024-09-16
1.6.6	0 / 11	2023-12-31
1.6.5	0 / 11	2023-04-12
1.6.4	0 / 11	2023-04-11
1.6.3	0 / 11	2023-02-03
1.6.2	0 / 11	2023-02-02
1.6.1	0 / 11	2023-02-02
1.6.0	0 / 11	2023-01-28
1.5.4	1 / 10	2022-07-01
1.5.3	1 / 10	2022-06-27
1.5.2	1 / 10	2022-06-27
1.5.1	1 / 10	2022-06-27
1.5.0	1 / 10	2022-06-25
1.4.1	1 / 7	2022-01-11
1.4.0	1 / 7	2022-01-08
1.3.0	1 / 7	2021-11-06

v1.9.1

1 finding

LOW No provenance attestation provenance

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

v1.9.0

1 finding

LOW No provenance attestation provenance

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

v1.8.9

1 finding

LOW No provenance attestation provenance

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

v1.8.8

1 finding

LOW No provenance attestation provenance

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

v1.7.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.

v1.6.6

1 finding

LOW No provenance attestation provenance

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

v1.6.5

1 finding

LOW No provenance attestation provenance

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

v1.6.4

1 finding

LOW No provenance attestation provenance

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

v1.6.3

1 finding

LOW No provenance attestation provenance

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

v1.6.2

1 finding

LOW No provenance attestation provenance

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

v1.6.1

1 finding

LOW No provenance attestation provenance

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

v1.6.0

1 finding

LOW No provenance attestation provenance

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

v1.5.4

1 finding

LOW No provenance attestation provenance

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

v1.5.3

1 finding

LOW No provenance attestation provenance

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

v1.5.2

1 finding

LOW No provenance attestation provenance

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

v1.5.1

1 finding

LOW No provenance attestation provenance

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

v1.5.0

1 finding

LOW No provenance attestation provenance

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

v1.4.1

1 finding

LOW No provenance attestation provenance

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

v1.4.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.

v1.3.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.