@edsis/angular
Angular library package for Edsis, including the generated SDK entry points:
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Metadata-only signals; established scoped monorepo package. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Minor metadata gap, not indicative of malware for this monorepo package. | ai | |
| source-diff | obfuscated-file:fesm2022/edsis-angular-block-themes.mjs | AI (source-diff): Minified fesm2022 bundle with legible imports; build output not obfuscation. | ai | |
| semgrep | semgrep:api-obfuscation-reflect | AI (semgrep): Reflect.get used for Tauri environment feature-detection, not API evasion. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Growth explained by addition of chart component (203KB mjs + map + types); no injected payload signals. | ai | |
| source-diff | large-new-source-files | AI (source-diff): Size increase attributable to new chart component bundle with D3/carousel deps; no malicious indicators. | ai | |
| source-diff | obfuscated-file:fesm2022/ojiepermana-angular-component-date-picker.mjs | AI (source-diff): fesm2022 bundles are standard Angular build output; sample shows readable Angular component code, not obfuscation. | ai | |
| source-diff | obfuscated-file:fesm2022/ojiepermana-angular-ui-component-date-picker.mjs | AI (source-diff): Standard Angular fesm2022 bundle with long lines from inlined templates; not obfuscated code. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Fires in a config-file loader that resolves by extension; standard pattern for this type of generator tooling. | ai | |
| phantom-deps | phantom-dep:tslib | AI (phantom-deps): tslib was removed as a dep in this version; phantom-dep finding is a stale artifact. | ai |
Versions (showing 51 of 53)
| Version | Deps | Published |
|---|---|---|
| 22.0.93 | 1 / 0 | |
| 22.0.91 | 1 / 0 | |
| 22.0.90 | 1 / 0 | |
| 22.0.89 | 1 / 0 | |
| 22.0.88 | 1 / 0 | |
| 22.0.87 | 1 / 0 | |
| 22.0.84 | 1 / 0 | |
| 22.0.82 | 1 / 0 | |
| 22.0.69 | 1 / 0 | |
| 22.0.68 | 1 / 0 | |
| 22.0.55 | 1 / 0 | |
| 22.0.41 | 1 / 0 | |
| 22.0.27 | 1 / 0 | |
| 22.0.26 | 1 / 0 | |
| 22.0.25 | 1 / 0 | |
| 22.0.24 | 1 / 0 | |
| 22.0.23 | 1 / 0 | |
| 22.0.14 | 1 / 0 | |
| 22.0.13 | 1 / 0 | |
| 22.0.12 | 1 / 0 | |
| 22.0.11 | 1 / 0 | |
| 22.0.10 | 1 / 0 | |
| 22.0.9 | 1 / 0 | |
| 22.0.8 | 1 / 0 | |
| 22.0.7 | 1 / 0 | |
| 22.0.6 | 1 / 0 | |
| 22.0.5 | 1 / 0 | |
| 22.0.4 | 1 / 0 | |
| 22.0.3 | 1 / 0 | |
| 22.0.2 | 1 / 0 | |
| 22.0.1 | 12 / 0 | |
| 21.3.15 | 1 / 0 | |
| 21.3.13 | 1 / 0 | |
| 21.3.12 | 1 / 0 | |
| 21.3.11 | 1 / 0 | |
| 21.3.10 | 1 / 0 | |
| 21.3.9 | 1 / 0 | |
| 21.3.8 | 1 / 0 | |
| 21.3.4 | 12 / 0 | |
| 21.3.3 | 12 / 0 | |
| 21.3.0 | 12 / 0 | |
| 21.2.4 | 12 / 0 | |
| 21.2.3 | 12 / 0 | |
| 21.1.31 | 10 / 0 | |
| 21.1.27 | 10 / 0 | |
| 21.1.4 | 1 / 0 | |
| 21.1.3 | 1 / 0 | |
| 21.1.2 | 1 / 0 | |
| 21.1.1 | 1 / 0 | |
| 21.0.1 | 1 / 0 | |
| 21.0.0 | 1 / 0 |
v22.0.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v22.0.82
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
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.
v22.0.69
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
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.
v22.0.68
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
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.
v22.0.55
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: ojiepermana.
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.
v22.0.41
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: ojiepermana.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.