@yamato-daiwa/es-extensions-nodejs
Additional to @yamato-daiwa/es-extensions functionality for Node.js environment. Helper functions and classes aimed to reduce the routine code. Build-in TypeScript type safety.
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
Keywords
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 1.9.1 | 5 / 8 | |
| 1.9.0 | 5 / 8 | |
| 1.8.9 | 5 / 8 | |
| 1.8.8 | 5 / 8 | |
| 1.8.7 | 5 / 8 | |
| 1.8.6 | 5 / 8 | |
| 1.8.5 | 5 / 8 | |
| 1.8.4 | 5 / 8 | |
| 1.8.3 | 5 / 8 | |
| 1.8.2 | 5 / 8 | |
| 1.8.1 | 5 / 9 | |
| 1.8.0 | 5 / 9 | |
| 1.7.0 | 5 / 10 | |
| 1.6.0 | 5 / 10 | |
| 1.5.3 | 2 / 8 | |
| 1.5.2 | 2 / 8 | |
| 1.5.1 | 2 / 8 | |
| 1.5.0 | 2 / 8 |
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.