@breadstone-infrastructure/nx-tasks
Common nx tasks
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@breadstone-tools/cem-plugins-expand-types | AI (phantom-deps): Config-file reference in nx tasks package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@breadstone-tools/openapi-core | AI (phantom-deps): Config-file reference in nx tasks package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@breadstone-tools/localizator-core | AI (phantom-deps): Config-file reference in nx tasks package; stable false positive. | ai | |
| phantom-deps | phantom-dep:@breadstone-tools/cem-app | AI (phantom-deps): Referenced in config files as expected for an nx tasks package; not a real phantom dep concern. | ai | |
| phantom-deps | phantom-dep:@breadstone-tools/cem-plugins-custom-js-doc-tags | AI (phantom-deps): Config-file reference in nx tasks package; stable false positive. | ai | |
| phantom-deps | phantom-dep:typedoc-plugin-markdown | AI (phantom-deps): typedoc-plugin-markdown is a config-referenced plugin, not directly imported in code; stable false positive for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Used in a release/publish executor task; shelling out is expected behavior for an Nx task runner package. | ai |
Versions (showing 51 of 118)
| Version | Deps | Published |
|---|---|---|
| 0.1.62 | 6 / 0 | |
| 0.1.61 | 6 / 0 | |
| 0.1.59 | 6 / 0 | |
| 0.1.58 | 6 / 0 | |
| 0.1.57 | 6 / 0 | |
| 0.1.56 | 6 / 0 | |
| 0.1.55 | 6 / 0 | |
| 0.1.54 | 6 / 0 | |
| 0.1.53 | 6 / 0 | |
| 0.1.52 | 6 / 0 | |
| 0.1.51 | 6 / 0 | |
| 0.1.50 | 6 / 0 | |
| 0.1.49 | 6 / 0 | |
| 0.1.48 | 6 / 0 | |
| 0.1.47 | 6 / 0 | |
| 0.1.46 | 6 / 0 | |
| 0.1.45 | 6 / 0 | |
| 0.1.44 | 6 / 0 | |
| 0.1.43 | 6 / 0 | |
| 0.1.42 | 6 / 0 | |
| 0.1.41 | 6 / 0 | |
| 0.1.40 | 6 / 0 | |
| 0.1.39 | 6 / 0 | |
| 0.1.38 | 6 / 0 | |
| 0.1.37 | 6 / 0 | |
| 0.1.36 | 6 / 0 | |
| 0.1.35 | 6 / 0 | |
| 0.1.33 | 6 / 0 | |
| 0.1.32 | 6 / 0 | |
| 0.1.31 | 6 / 0 | |
| 0.1.30 | 6 / 0 | |
| 0.1.28 | 6 / 0 | |
| 0.1.27 | 6 / 0 | |
| 0.1.26 | 6 / 0 | |
| 0.1.25 | 6 / 0 | |
| 0.1.23 | 6 / 0 | |
| 0.1.22 | 6 / 0 | |
| 0.1.21 | 6 / 0 | |
| 0.1.20 | 6 / 0 | |
| 0.1.19 | 6 / 0 | |
| 0.1.18 | 6 / 0 | |
| 0.1.17 | 6 / 0 | |
| 0.1.16 | 6 / 0 | |
| 0.1.15 | 6 / 0 | |
| 0.1.14 | 6 / 0 | |
| 0.1.13 | 6 / 0 | |
| 0.1.12 | 6 / 0 | |
| 0.1.11 | 6 / 0 | |
| 0.1.10 | 6 / 0 | |
| 0.1.9 | 6 / 0 | |
| 0.1.8 | 6 / 0 |
v0.1.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.59
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.