@po-ui/ng-components MIT 61 versions

@po-ui/ng-components

npm Repository Homepage

PO UI - Components

61

Versions

MIT

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, so a manually published version cannot be tied back to a reviewed commit.

Maintainers

pouidevalinelariguetpedrodominguestotvs

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:types/po-ui-ng-components.d.ts	AI (source-diff): Large bundled .d.ts type declarations, not obfuscated executable code.	ai	2026/07/21
phantom-deps	phantom-dep:echarts	AI (phantom-deps): echarts is a known optional chart dep in this Angular library; lazy-loaded pattern means no direct import.	ai	2026/06/02
phantom-deps	phantom-dep:driver.js	AI (phantom-deps): driver.js is a legitimate tour library; phantom-dep likely reflects Angular DI/lazy usage pattern.	ai	2026/06/02
phantom-deps	phantom-dep:@po-ui/style	AI (phantom-deps): Same-org style package; consumed as a CSS/asset dep, not a JS import.	ai	2026/06/02

Versions (showing 61 of 61)

Version	Deps	Published
21.25.0	6 / 0	2026/07/24
21.24.0	6 / 0	2026-07-21
21.23.1	6 / 0	2026-07-14
21.23.0	6 / 0	2026-07-06
21.22.0	6 / 0	2026-06-25
21.21.0	6 / 0	2026-06-18
21.20.0	6 / 0	2026-06-15
21.19.0	6 / 0	2026-06-05
21.18.0	6 / 0	2026-06-01
21.17.0	5 / 0	2026-05-25
21.16.0	5 / 0	2026-05-18
21.15.0	5 / 0	2026-05-14
21.14.0	5 / 0	2026-05-08
21.13.1	5 / 0	2026-05-05
21.13.0	5 / 0	2026-05-04
21.12.0	5 / 0	2026-04-27
21.11.0	5 / 0	2026-04-23
21.10.0	5 / 0	2026-04-16
21.9.0	5 / 0	2026-04-09
21.8.0	5 / 0	2026-04-01
21.7.0	5 / 0	2026-03-26
21.6.0	5 / 0	2026-03-17
21.5.0	5 / 0	2026-03-10
21.4.0	5 / 0	2026-03-03
21.3.0	5 / 0	2026-02-23
21.2.0	5 / 0	2026-02-12
21.1.0	5 / 0	2026-02-03
21.0.1	5 / 0	2026-01-29
21.0.0	5 / 0	2026-01-28
20.13.1	5 / 0	2026-01-26
20.13.0	5 / 0	2026-01-12
20.12.0	5 / 0	2025-12-18
20.11.0	5 / 0	2025-12-01
20.10.0	5 / 0	2025-11-25
20.9.0	5 / 0	2025-11-10
20.8.0	5 / 0	2025-11-03
19.39.19	5 / 0	2026-07-21
19.39.18	5 / 0	2026-07-14
19.39.17	5 / 0	2026-07-06
19.39.16	5 / 0	2026-06-25
19.39.15	5 / 0	2026-06-15
19.39.14	5 / 0	2026-06-05
19.39.13	5 / 0	2026-06-01
19.39.12	5 / 0	2026-05-25
19.39.11	5 / 0	2026-05-14
19.39.10	5 / 0	2026-04-28
19.39.9	5 / 0	2026-04-23
19.39.8	5 / 0	2026-04-16
19.39.7	5 / 0	2026-03-26
19.39.6	5 / 0	2026-03-10
19.39.5	5 / 0	2026-03-03
19.39.4	5 / 0	2026-02-23
19.39.3	5 / 0	2026-02-12
19.39.2	5 / 0	2026-02-03
19.39.1	5 / 0	2026-01-26
19.39.0	5 / 0	2026-01-12
19.38.0	5 / 0	2025-12-18
19.37.0	5 / 0	2025-12-01
19.36.0	5 / 0	2025-11-25
19.35.0	5 / 0	2025-11-10
19.34.0	5 / 0	2025-11-03

v21.25.0

1 finding

LOW No provenance attestation provenance

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

v21.24.0

2 findings

HIGH New obfuscated file: types/po-ui-ng-components.d.ts 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.23.1

1 finding

LOW No provenance attestation provenance

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

v21.23.0

1 finding

LOW No provenance attestation provenance

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

v21.7.0

2 findings

HIGH New obfuscated file: types/po-ui-ng-components.d.ts 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.6.0

2 findings

HIGH New obfuscated file: types/po-ui-ng-components.d.ts 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.5.0

2 findings

HIGH New obfuscated file: types/po-ui-ng-components.d.ts 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.4.0

2 findings

HIGH New obfuscated file: types/po-ui-ng-components.d.ts 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: types/po-ui-ng-components.d.ts 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.0

2 findings

HIGH New obfuscated file: types/po-ui-ng-components.d.ts 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.1.0

2 findings

HIGH New obfuscated file: types/po-ui-ng-components.d.ts 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.0.1

2 findings

HIGH New obfuscated file: types/po-ui-ng-components.d.ts 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.0.0

2 findings

HIGH New obfuscated file: types/po-ui-ng-components.d.ts 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.

v20.13.1

1 finding

LOW No provenance attestation provenance

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

v20.13.0

1 finding

LOW No provenance attestation provenance

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

v20.12.0

1 finding

LOW No provenance attestation provenance

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

v20.11.0

1 finding

LOW No provenance attestation provenance

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

v20.10.0

1 finding

LOW No provenance attestation provenance

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

v20.9.0

1 finding

LOW No provenance attestation provenance

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

v20.8.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.

v19.39.19

1 finding

LOW No provenance attestation provenance

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

v19.39.18

1 finding

LOW No provenance attestation provenance

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

v19.39.17

1 finding

LOW No provenance attestation provenance

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

v19.39.7

1 finding

LOW No provenance attestation provenance

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

v19.39.6

1 finding

LOW No provenance attestation provenance

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

v19.39.5

1 finding

LOW No provenance attestation provenance

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

v19.39.4

1 finding

LOW No provenance attestation provenance

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

v19.39.3

1 finding

LOW No provenance attestation provenance

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

v19.39.2

1 finding

LOW No provenance attestation provenance

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

v19.39.1

1 finding

LOW No provenance attestation provenance

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

v19.39.0

1 finding

LOW No provenance attestation provenance

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

v19.38.0

1 finding

LOW No provenance attestation provenance

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

v19.37.0

1 finding

LOW No provenance attestation provenance

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

v19.36.0

1 finding

LOW No provenance attestation provenance

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

v19.35.0

1 finding

LOW No provenance attestation provenance

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

v19.34.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.