@progress-chef/platform-code-gen-store-services
This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 16.2.0.
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:esm2022/lib/chef-license-management-service/actions/action-types.codegen.mjs | AI (source-diff): Codegen enum output, readable code. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-license-management-service/actions/action-declarations.codegen.mjs | AI (source-diff): Bundled Angular build output with sourcemap to readable ts source. | ai | |
| source-diff | obfuscated-file:lib/chef-license-management-service/actions/action-declarations.codegen.d.ts | AI (source-diff): Angular codegen d.ts, single-line type union, not obfuscation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Routine maintainer turnover on long-lived internal codegen package. | ai | |
| provenance | publisher-changed | AI (provenance): CI-based publisher (GitHub Actions) consistent with automated release pipeline. | ai | |
| source-diff | obfuscated-file:lib/chef-dsm-store-service/actions/action-declarations.codegen.d.ts | AI (source-diff): Long-line codegen'd TS union types, not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-courier-scheduler/actions/action-declarations.codegen.mjs | AI (source-diff): Long-line codegen output with sourcemap, not obfuscation; consistent with codegen package purpose. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Publisher is an existing known maintainer per provenance INFO finding. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Expected growth from generated codegen modules, not injected code. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/effects/tenant.effects.codegen.mjs | AI (source-diff): Same pattern as other effects files; standard Angular codegen output. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/effects/token.effects.codegen.mjs | AI (source-diff): Same pattern as other effects files; standard Angular codegen output. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/effects/users.effects.codegen.mjs | AI (source-diff): Same pattern as other effects files; standard Angular codegen output. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/models/schemas.codegen.mjs | AI (source-diff): Codegen schema file; long lines expected from generated model definitions. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/actions/action-declarations.codegen.mjs | AI (source-diff): Long lines are inline base64 sourceMappingURL, standard Angular library build output, not obfuscation. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/requests/identityproviders.requests.codegen.mjs | AI (source-diff): Same pattern as other request files; standard Angular codegen output. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/requests/users.requests.codegen.mjs | AI (source-diff): Same pattern as other request files; standard Angular codegen output. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a declared runtime dependency used implicitly by Angular/TypeScript compiled output; stable false positive. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/requests/configuration.requests.codegen.mjs | AI (source-diff): Standard Angular HTTP request service codegen; long lines from chained operators. | ai | |
| source-diff | obfuscated-file:lib/chef-sso/actions/action-declarations.codegen.d.ts | AI (source-diff): Long line is a TypeScript union type declaration from codegen; not obfuscated code. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/actions/action-types.codegen.mjs | AI (source-diff): Readable NgRx action type enum; long line is dense but not obfuscated. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/actions/configuration.actions.codegen.mjs | AI (source-diff): Standard Angular codegen action classes; long lines from inline source maps. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/actions/identityproviders.actions.codegen.mjs | AI (source-diff): Standard Angular codegen action classes; long lines from inline source maps. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/actions/tenant.actions.codegen.mjs | AI (source-diff): Standard Angular codegen action classes; long lines from inline source maps. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/actions/users.actions.codegen.mjs | AI (source-diff): Standard Angular codegen action classes; long lines from inline source maps. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/effects/configuration.effects.codegen.mjs | AI (source-diff): Readable NgRx effects using createEffect/ofType; long lines are chained RxJS operators, not obfuscation. | ai | |
| source-diff | obfuscated-file:esm2022/lib/chef-sso/effects/identityproviders.effects.codegen.mjs | AI (source-diff): Same pattern as other effects files; standard Angular codegen output. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 1.2.3 | 1 / 0 | |
| 1.2.2 | 1 / 0 | |
| 1.2.1 | 1 / 0 | |
| 1.2.0 | 1 / 0 | |
| 1.1.1 | 1 / 0 | |
| 1.1.0 | 1 / 0 | |
| 1.0.73 | 1 / 0 | |
| 1.0.72 | 1 / 0 | |
| 1.0.71 | 1 / 0 | |
| 1.0.70 | 1 / 0 | |
| 1.0.69 | 1 / 0 | |
| 1.0.68 | 1 / 0 | |
| 1.0.67 | 1 / 0 | |
| 1.0.66 | 1 / 0 | |
| 1.0.65 | 1 / 0 | |
| 1.0.64 | 1 / 0 | |
| 1.0.63 | 1 / 0 | |
| 1.0.62 | 1 / 0 | |
| 1.0.61 | 1 / 0 | |
| 1.0.60 | 1 / 0 | |
| 1.0.59 | 1 / 0 | |
| 1.0.58 | 1 / 0 | |
| 1.0.57 | 1 / 0 | |
| 1.0.56 | 1 / 0 | |
| 1.0.55 | 1 / 0 | |
| 1.0.54 | 1 / 0 | |
| 1.0.53 | 1 / 0 | |
| 1.0.52 | 1 / 0 | |
| 1.0.51 | 1 / 0 | |
| 1.0.50 | 1 / 0 | |
| 1.0.49 | 1 / 0 | |
| 1.0.48 | 1 / 0 | |
| 1.0.47 | 1 / 0 | |
| 1.0.46 | 1 / 0 | |
| 1.0.45 | 1 / 0 | |
| 1.0.44 | 1 / 0 | |
| 1.0.42 | 1 / 0 | |
| 1.0.37 | 1 / 0 | |
| 1.0.33 | 1 / 0 | |
| 1.0.32 | 1 / 0 | |
| 1.0.31 | 1 / 0 | |
| 1.0.27 | 1 / 0 | |
| 1.0.26 | 1 / 0 | |
| 1.0.25 | 1 / 0 | |
| 1.0.24 | 1 / 0 | |
| 1.0.23 | 1 / 0 | |
| 1.0.2 | 1 / 0 | |
| 1.0.1 | 1 / 0 |
v1.0.44
13 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.0.42
13 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.0.37
14 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
This version was published by a different npm account (anees-progress) than the most recent previously approved version (vaigadre19) on 2025-02-07, but anees-progress is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.27
18 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
This version was published by a different npm account (nichite_aadesh) than the most recent previously approved version (vaigadre19) on 2024-06-11, but nichite_aadesh is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.26
18 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
Newly 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.
This version was published by a different npm account (vaigadre19) than the most recent previously approved version (nichite_aadesh) on 2024-06-06, but vaigadre19 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.25
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (vaigadre19) than the most recent previously approved version (nichite_aadesh) on 2024-05-31, but vaigadre19 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v1.0.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.