@po-ui/ng-code-editor MIT 49 versions

@po-ui/ng-code-editor

npm Repository Homepage

PO UI - Code Editor

49

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 — the axios compromise (March 2026) relied on exactly this gap.

Maintainers

pouidevalinelariguetpedrodominguestotvs

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
maintainer-change	maintainer-added	AI (maintainer-change): Publisher pouidev has strong approval track record; org-level team change for established po-ui package.	ai	2026/05/22
maintainer-change	maintainer-removed	AI (maintainer-change): Bulk removal consistent with org restructuring, not a hostile takeover; no code changes detected.	ai	2026/05/22
publish-pattern	dormant-publish	AI (publish-pattern): Established package with 380 versions; dormancy followed by org-level team change is consistent with normal maintenance cycles.	ai	2026/05/22
phantom-deps	phantom-dep:tslib	AI (phantom-deps): tslib is a known implicit Angular/TypeScript runtime dep; not directly imported by design.	ai	2026/04/29
phantom-deps	phantom-dep:monaco-editor	AI (phantom-deps): monaco-editor is a peer/config dependency for the code editor component; indirect usage is expected.	ai	2026/04/29
phantom-deps	phantom-dep:core-js	AI (phantom-deps): core-js is a standard polyfill used implicitly by Angular build toolchain.	ai	2026/04/29
phantom-deps	phantom-dep:intl	AI (phantom-deps): intl is referenced in config files as a polyfill; not directly imported by design.	ai	2026/04/29

Versions (showing 49 of 49)

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

v21.19.0

1 finding

LOW No provenance attestation provenance

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

v21.18.0

1 finding

LOW No provenance attestation provenance

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

v21.17.0

1 finding

LOW No provenance attestation provenance

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

v21.16.0

1 finding

LOW No provenance attestation provenance

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

v21.15.0

1 finding

LOW No provenance attestation provenance

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

v21.14.0

1 finding

LOW No provenance attestation provenance

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

v21.13.1

1 finding

LOW No provenance attestation provenance

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

v21.13.0

1 finding

LOW No provenance attestation provenance

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

v21.11.0

1 finding

LOW No provenance attestation provenance

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

v21.10.0

1 finding

LOW No provenance attestation provenance

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

v21.9.0

1 finding

LOW No provenance attestation provenance

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

v21.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.

v21.7.0

1 finding

LOW No provenance attestation provenance

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

v21.6.0

1 finding

LOW No provenance attestation provenance

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

v21.5.0

1 finding

LOW No provenance attestation provenance

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

v21.4.0

1 finding

LOW No provenance attestation provenance

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

v21.3.0

1 finding

LOW No provenance attestation provenance

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

v21.2.0

1 finding

LOW No provenance attestation provenance

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

v21.1.0

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. Consider requesting the maintainer enable provenance via CI/CD.

v21.0.0

1 finding

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.14

1 finding

LOW No provenance attestation provenance

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

v19.39.13

1 finding

LOW No provenance attestation provenance

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

v19.39.12

1 finding

LOW No provenance attestation provenance

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

v19.39.11

1 finding

LOW No provenance attestation provenance

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

v19.39.10

1 finding

LOW No provenance attestation provenance

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

v19.39.9

1 finding

LOW No provenance attestation provenance

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

v19.39.8

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. Only ~12% of npm packages have provenance, so this is common but not ideal.

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.