@nevware21/ts-async
support for asynchronous development with a Promise based task Scheduler, several different Promise implementations (synchronous, idle, asynchronous and native runtime wrappers), await helpers, and aliases all built and tested using TypeScript.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@nevware21/tools-pre-proc | AI (phantom-deps): Same-org build-tool used only in build scripts, not runtime import. | ai | |
| dependencies | unvetted-dep:@nevware21/tools-pre-proc | AI (dependencies): Same-org build tooling, low-risk build-time-only dependency. | ai | |
| provenance | no-provenance | AI (provenance): Established package from a known org; lack of provenance is common and not a risk indicator for this publisher. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 0.6.1 | 1 / 35 | |
| 0.6.0 | 1 / 35 | |
| 0.5.5 | 1 / 40 | |
| 0.5.4 | 1 / 39 | |
| 0.5.3 | 1 / 39 | |
| 0.5.2 | 1 / 39 | |
| 0.5.1 | 1 / 39 | |
| 0.5.0 | 1 / 39 | |
| 0.4.0 | 1 / 38 | |
| 0.3.0 | 1 / 38 | |
| 0.2.6 | 1 / 38 | |
| 0.2.5 | 2 / 37 | |
| 0.2.4 | 1 / 37 | |
| 0.2.3 | 1 / 37 | |
| 0.2.2 | 1 / 37 | |
| 0.2.1 | 1 / 37 | |
| 0.2.0 | 1 / 37 | |
| 0.1.2 | 1 / 37 | |
| 0.1.1 | 1 / 35 | |
| 0.1.0 | 0 / 31 |
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.3
2 findingsThis version was published by a different npm account (nevware21bot) than the most recent previously approved version (nev21) on 2023-04-25. It has since remained available on npm for 1182 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.