@nx/powerpack-enterprise-cloud
A Nx Powerpack plugin which is specific to Nx Enterprise Cloud workspaces.
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | missing-githead | AI (provenance): Nx org publishes via GitHub Actions; gitHead absence is a CI config change, not a security signal for this package. | ai | |
| provenance | no-provenance | AI (provenance): Nx powerpack packages consistently lack Sigstore attestation; stable false-positive for this package family. | ai | |
| license | uncommon-license:Commercial | AI (license): Commercial license is intentional for Nx Powerpack; stable across all versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require is a byproduct of the intentional obfuscation in this commercial Nx plugin; not a standalone risk. | ai | |
| semgrep | semgrep:obfuscation-while-true | AI (semgrep): Commercial closed-source Nx plugin; intentional obfuscation is consistent with license and publisher pattern across all versions. | ai |
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 5.0.7 | 1 / 0 | |
| 5.0.6 | 1 / 0 | |
| 5.0.5 | 1 / 0 | |
| 5.0.4 | 1 / 0 | |
| 5.0.3 | 1 / 0 | |
| 5.0.2 | 1 / 0 | |
| 5.0.1 | 1 / 0 | |
| 5.0.0 | 1 / 0 |
v5.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.6
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
2 findingswhile(!![]) loop is a signature of javascript-obfuscator output > 1 | 'use strict';var a0_0x314fc3=a0_0x3d16;(function(_0x2ae4f7,_0x5272ea){var _0x5d2135=a0_0x3d16,_0x2b2ee9=_0x2ae4f7();whil
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.1
2 findingswhile(!![]) loop is a signature of javascript-obfuscator output > 1 | 'use strict';var a0_0x426a57=a0_0x2904;(function(_0x4a2fd0,_0x501be2){var _0x2f63e7=a0_0x2904,_0x39421e=_0x4a2fd0();whil
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
2 findingswhile(!![]) loop is a signature of javascript-obfuscator output > 1 | 'use strict';var a0_0xce605=a0_0x6195;function a0_0x6195(_0x56d419,_0x425302){var _0x364fa2=a0_0x364f();return a0_0x6195
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.