@acorex/platform-generator
This library was generated with [Nx](https://nx.dev).
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): CLI generator tool; child_process/spawn is expected for interactive scaffolding binary. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal monorepo tooling package; sparse metadata is consistent across 207 published versions. | ai |
Versions (showing 41 of 41)
| Version | Deps | Published |
|---|---|---|
| 20.8.9 | 0 / 0 | |
| 20.8.8 | 0 / 0 | |
| 20.8.7 | 0 / 0 | |
| 20.8.6 | 0 / 0 | |
| 20.8.5 | 0 / 0 | |
| 20.8.4 | 0 / 0 | |
| 20.8.3 | 0 / 0 | |
| 20.8.1 | 0 / 0 | |
| 20.7.22 | 0 / 0 | |
| 20.7.21 | 0 / 0 | |
| 20.7.20 | 0 / 0 | |
| 20.7.19 | 0 / 0 | |
| 20.7.17 | 0 / 0 | |
| 20.7.16 | 0 / 0 | |
| 20.7.15 | 0 / 0 | |
| 20.7.13 | 0 / 0 | |
| 20.7.12 | 0 / 0 | |
| 20.7.11 | 0 / 0 | |
| 20.7.10 | 0 / 0 | |
| 20.7.9 | 0 / 0 | |
| 20.7.8 | 0 / 0 | |
| 20.7.7 | 0 / 0 | |
| 20.7.6 | 0 / 0 | |
| 20.7.5 | 0 / 0 | |
| 20.7.4 | 0 / 0 | |
| 20.7.3 | 0 / 0 | |
| 20.7.2 | 0 / 0 | |
| 20.6.8 | 0 / 0 | |
| 20.6.7 | 0 / 0 | |
| 20.6.6 | 0 / 0 | |
| 20.6.5 | 0 / 0 | |
| 20.6.4 | 0 / 0 | |
| 20.6.3 | 0 / 0 | |
| 20.6.2 | 0 / 0 | |
| 20.6.1 | 0 / 0 | |
| 20.6.0 | 0 / 0 | |
| 20.5.4 | 0 / 0 | |
| 20.5.3 | 0 / 0 | |
| 20.5.2 | 0 / 0 | |
| 20.5.1 | 0 / 0 | |
| 20.4.2 | 0 / 0 |
v20.7.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.6.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.6.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.6.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.6.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.