@harnessio/react-ng-manager-swagger-service-client
Harness React NG Manager Swagger service client - NG Manager APIs integrated with react hooks
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:dist/ng-manager-swagger-service/src/services/hooks/useListAllEntityUsageByFqnQuery.d.ts | AI (source-diff): Long lines are TypeScript union type literals in auto-generated .d.ts files, not obfuscation. | ai | |
| source-diff | obfuscated-file:dist/ng-manager-swagger-service/src/services/schemas/EntityDetail.d.ts | AI (source-diff): Same pattern: auto-generated union type enum in .d.ts; stable false positive for this swagger-generated package. | ai | |
| phantom-deps | phantom-dep:pnpm | AI (phantom-deps): pnpm listed as dependency for workspace tooling, not a runtime import; stable false positive. | ai |
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 1.22.0 | 1 / 0 | |
| 1.21.0 | 1 / 0 | |
| 1.20.1 | 1 / 0 | |
| 1.20.0 | 1 / 0 | |
| 1.19.0 | 1 / 0 | |
| 1.18.0 | 1 / 0 | |
| 1.17.0 | 1 / 0 | |
| 1.16.0 | 1 / 0 | |
| 1.15.0 | 1 / 0 | |
| 1.14.0 | 1 / 0 | |
| 1.13.0 | 1 / 0 | |
| 1.12.0 | 1 / 0 | |
| 1.11.0 | 1 / 0 | |
| 1.10.0 | 1 / 0 | |
| 1.9.0 | 1 / 0 | |
| 1.8.0 | 1 / 0 | |
| 1.7.1 | 1 / 0 | |
| 1.7.0 | 1 / 0 | |
| 1.6.2 | 1 / 0 | |
| 1.6.1 | 1 / 0 | |
| 1.6.0 | 1 / 0 | |
| 1.5.1 | 1 / 0 | |
| 1.5.0 | 1 / 0 | |
| 1.4.1 | 1 / 0 | |
| 1.4.0 | 1 / 0 |
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.1
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package 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.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.