@edsis/angular No license 33 versions

@edsis/angular

npm

Angular library package for Edsis, including the generated SDK entry points:

33

Versions

—

License

No

Install Scripts

Missing

Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures gitHead linked

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

ojiepermana

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
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	2026/06/04
source-diff	source-size-tripled	AI (source-diff): Growth explained by addition of chart component (203KB mjs + map + types); no injected payload signals.	ai	2026/06/04
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	2026/05/30
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	2026/05/26
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	2026/05/19
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	2026/05/19

Versions (showing 33 of 33)

Version	Deps	Published
22.0.11	1 / 0	2026-06-06
22.0.10	1 / 0	2026-06-06
22.0.9	1 / 0	2026-06-06
22.0.8	1 / 0	2026-06-06
22.0.7	1 / 0	2026-06-06
22.0.6	1 / 0	2026-06-06
22.0.5	1 / 0	2026-06-06
22.0.4	1 / 0	2026-06-04
22.0.3	1 / 0	2026-06-03
22.0.2	1 / 0	2026-06-03
22.0.1	12 / 0	2026-06-03
21.3.15	1 / 0	2026-06-01
21.3.13	1 / 0	2026-05-31
21.3.12	1 / 0	2026-05-31
21.3.11	1 / 0	2026-05-31
21.3.10	1 / 0	2026-05-31
21.3.9	1 / 0	2026-05-31
21.3.8	1 / 0	2026-05-30
21.3.4	12 / 0	2026-05-24
21.3.3	12 / 0	2026-05-23
21.3.0	12 / 0	2026-05-23
21.2.4	12 / 0	2026-05-23
21.2.3	12 / 0	2026-05-23
21.1.31	10 / 0	2026-05-21
21.1.27	10 / 0	2026-05-18
21.1.4	1 / 0	2026-05-17
21.1.3	1 / 0	2026-04-27
21.1.2	1 / 0	2026-04-27
21.1.1	1 / 0	2026-04-27
21.0.1	1 / 0	2026-04-21
21.0.0	1 / 0	2026-04-21
0.0.2	1 / 0	2026-04-14
0.0.1	1 / 0	2026-04-14

v22.0.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v22.0.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v22.0.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v22.0.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v22.0.7

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v22.0.6

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v22.0.5

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v22.0.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v22.0.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v22.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v22.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.3.15

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.3.13

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.3.12

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.3.11

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.3.10

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.3.9

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.3.8

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.3.4

2 findings

HIGH New obfuscated file: fesm2022/ojiepermana-angular-component-date-picker.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.3.3

2 findings

HIGH New obfuscated file: fesm2022/ojiepermana-angular-component-date-picker.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.3.0

2 findings

HIGH New obfuscated file: fesm2022/ojiepermana-angular-ui-component-date-picker.mjs source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.2.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.2.3

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.1.31

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.1.27

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.1.4

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.1.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.1.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v21.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v21.0.0

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.2

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v0.0.1

1 finding

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.