@nx/powerpack-license
Package to provide the ability to activate and read licenses for Nx Powerpack.
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 |
|---|---|---|---|---|
| license | uncommon-license:Commercial | AI (license): Commercial license is expected for Nx Powerpack; stable across all versions. | ai | |
| semgrep | semgrep:obfuscation-while-true | AI (semgrep): Commercial license enforcement package; intentional obfuscation of proprietary license-check logic is expected and stable across versions. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require in obfuscated license-check code; consistent with the package's purpose, not arbitrary module loading. | ai | |
| bogus-package | bogus-package | AI (bogus-package): README links to official nx.dev docs; no-keywords is intentional for a commercial SDK sub-package. | ai | |
| phantom-deps | phantom-dep:@nx/key | AI (phantom-deps): @nx/key is a declared dependency in the same org scope; phantom-dep heuristic is a false positive here. | 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 findingPackage 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 | function a0_0x58d8(_0x23a6a5,_0xe01169){var _0x3db67f=a0_0x3db6();return a0_0x58d8=function(_0x58d831,_0xb03fff){_0x58d8
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 | function a0_0x5af6(){var _0x2cda77=['3062230iJxetK','34744oRzUyF','4646887RPGnni','2079PFPsPp','2110820XEoVZQ','2137980Q
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 | function a0_0x4079(_0x4e652e,_0x1e72ad){var _0x2bda80=a0_0x2bda();return a0_0x4079=function(_0x40798a,_0x4bd82b){_0x4079
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.