@temporalio/nyc-test-coverage
Temporal.io SDK code coverage integration
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 |
|---|---|---|---|---|
| npm-metadata | url-dep:@temporalio/common | AI (npm-metadata): Monorepo sibling ref, standard for this package's workspace structure. | ai | |
| npm-metadata | url-dep:@temporalio/worker | AI (npm-metadata): Monorepo sibling ref, standard for this package's workspace structure. | ai | |
| npm-metadata | url-dep:@temporalio/workflow | AI (npm-metadata): Monorepo sibling ref, standard for this package's workspace structure. | ai | |
| provenance | missing-githead | AI (provenance): Temporal SDK team publish environment change; package is otherwise clean with no other risk signals. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 1.21.0 | 4 / 9 | |
| 1.20.3 | 4 / 9 | |
| 1.20.2 | 4 / 9 | |
| 1.20.1 | 4 / 9 | |
| 1.20.0 | 4 / 9 | |
| 1.19.1 | 4 / 9 | |
| 1.19.0 | 4 / 9 | |
| 1.18.2 | 4 / 9 | |
| 1.18.1 | 4 / 9 | |
| 1.18.0 | 4 / 9 | |
| 1.17.5 | 4 / 9 | |
| 1.17.4 | 4 / 9 | |
| 1.17.3 | 4 / 9 | |
| 1.17.2 | 4 / 9 | |
| 1.17.1 | 4 / 8 | |
| 1.17.0 | 4 / 8 | |
| 1.16.3 | 4 / 8 | |
| 1.16.2 | 4 / 8 | |
| 1.16.1 | 4 / 8 | |
| 1.16.0 | 4 / 8 | |
| 1.15.1 | 4 / 8 | |
| 1.15.0 | 4 / 8 | |
| 1.14.2 | 4 / 8 | |
| 1.14.1 | 4 / 8 | |
| 1.14.0 | 4 / 8 | |
| 1.13.2 | 4 / 8 | |
| 1.13.1 | 4 / 8 | |
| 1.13.0 | 4 / 8 | |
| 1.12.3 | 4 / 8 | |
| 1.12.2 | 4 / 8 | |
| 1.12.1 | 4 / 8 | |
| 1.12.0 | 4 / 8 | |
| 1.11.8 | 4 / 8 | |
| 1.11.7 | 4 / 8 | |
| 1.11.6 | 4 / 8 | |
| 1.11.5 | 4 / 8 | |
| 1.11.4 | 4 / 8 | |
| 1.11.3 | 4 / 8 | |
| 1.11.2 | 4 / 8 | |
| 1.11.1 | 4 / 8 | |
| 1.11.0 | 4 / 8 | |
| 1.10.3 | 4 / 8 | |
| 1.10.2 | 4 / 8 | |
| 1.10.1 | 4 / 8 | |
| 1.10.0 | 4 / 8 |
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.