@sunbird-cb/cbp-ai
This library was generated with [Angular CLI](https://github.com/angular/angular-cli) version 8.2.14.
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/components/publish-request-form/publish-approve-request-form.component.mjs | AI (source-diff): Angular compiled ESM output; long lines are normal inline template compilation, not obfuscation. | ai | |
| source-diff | obfuscated-file:esm2022/lib/components/publish-request-form/publish-request-form.component.mjs | AI (source-diff): Angular ivy ESM2022 compiled output; long lines are template compilation artifacts, not obfuscation. | ai | |
| source-diff | obfuscated-file:esm2022/lib/components/reject-item-request-form/reject-item-request-form.component.mjs | AI (source-diff): Angular ivy ESM2022 compiled output; long lines are template compilation artifacts, not obfuscation. | ai | |
| source-diff | obfuscated-file:esm2022/lib/components/reject-request-form/reject-request-form.component.mjs | AI (source-diff): Angular ivy ESM2022 compiled output; long lines are template compilation artifacts, not obfuscation. | ai | |
| source-diff | obfuscated-file:esm2022/lib/components/designation-approval-request-form/designation-approval-request-form.component.mjs | AI (source-diff): Angular compiled ESM output; long lines are from template inlining, not obfuscation. Stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib is a standard Angular library runtime dep; phantom-dep false positive for this package. | ai |
Versions (showing 51 of 104)
| Version | Deps | Published |
|---|---|---|
| 0.1.105 | 1 / 0 | |
| 0.1.104 | 1 / 0 | |
| 0.1.103 | 1 / 0 | |
| 0.1.102 | 1 / 0 | |
| 0.1.101 | 1 / 0 | |
| 0.1.100 | 1 / 0 | |
| 0.1.99 | 1 / 0 | |
| 0.1.98 | 1 / 0 | |
| 0.1.97 | 1 / 0 | |
| 0.1.95 | 1 / 0 | |
| 0.1.94 | 1 / 0 | |
| 0.1.93 | 1 / 0 | |
| 0.1.92 | 1 / 0 | |
| 0.1.91 | 1 / 0 | |
| 0.1.90 | 1 / 0 | |
| 0.1.89 | 1 / 0 | |
| 0.1.88 | 1 / 0 | |
| 0.1.87 | 1 / 0 | |
| 0.1.86 | 1 / 0 | |
| 0.1.85 | 1 / 0 | |
| 0.1.84 | 1 / 0 | |
| 0.1.83 | 1 / 0 | |
| 0.1.82 | 1 / 0 | |
| 0.1.81 | 1 / 0 | |
| 0.1.80 | 1 / 0 | |
| 0.1.79 | 1 / 0 | |
| 0.1.78 | 1 / 0 | |
| 0.1.77 | 1 / 0 | |
| 0.1.76 | 1 / 0 | |
| 0.1.75 | 1 / 0 | |
| 0.1.74 | 1 / 0 | |
| 0.1.73 | 1 / 0 | |
| 0.1.72 | 1 / 0 | |
| 0.1.71 | 1 / 0 | |
| 0.1.70 | 1 / 0 | |
| 0.1.69 | 1 / 0 | |
| 0.1.68 | 1 / 0 | |
| 0.1.67 | 1 / 0 | |
| 0.1.66 | 1 / 0 | |
| 0.1.65 | 1 / 0 | |
| 0.1.64 | 1 / 0 | |
| 0.1.63 | 1 / 0 | |
| 0.1.62 | 1 / 0 | |
| 0.1.61 | 1 / 0 | |
| 0.1.60 | 1 / 0 | |
| 0.1.59 | 1 / 0 | |
| 0.1.58 | 1 / 0 | |
| 0.1.57 | 1 / 0 | |
| 0.1.56 | 1 / 0 | |
| 0.1.55 | 1 / 0 | |
| 0.1.54 | 1 / 0 |
v0.1.105
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.89
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 (vishnubansaltarento) than the most recent previously approved version (abhishekkp) on 2026-07-01, but vishnubansaltarento 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.