← Home

@agorapulse/ui-components

npm Repository Homepage
51
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

jvdreanfloppysamuelatagoratristanboujuwalidjekgepblanciauxtubulinenicolasjmusketyrmaxatagorajulien.descorpskarimdiboagorapulsegaetanrannounicolashorvatmarc-agorathelegendarrysbessah87hacenekedjarlfaurenicotsoomarouelheziamina.khaldimarcoprietosantosantoineagorapulseedenpulseagorapulse-webmasterbachir077kkoo95jvagorapulsekmecninmaelitopfloriansara-agorapulseaxelagoraedino_kunmalek.benazzouzaxeldadzsebastiengdusandra2audreyalexandremehdi-bensalhaceline-chaderdidiertnthaidangibrahim-08youneshamdanesandrafrade

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:fesm2022/agorapulse-ui-components-radio-button-card.mjs AI (source-diff): Standard Angular FESM2022 compiled output; long lines are inlined templates/metadata, not obfuscation. ai
source-diff obfuscated-file:fesm2022/agorapulse-ui-components-filter-chips-list.mjs AI (source-diff): Angular FESM2022 compiled output with long lines from inlined templates; not obfuscation. Stable pattern for this package. ai
source-diff obfuscated-file:fesm2022/agorapulse-ui-components-selection-dropdown.mjs AI (source-diff): Standard Angular FESM2022 build output; long lines are inlined templates/metadata, not obfuscation. ai
source-diff obfuscated-file:fesm2022/agorapulse-ui-components-tabs.mjs AI (source-diff): Standard Angular FESM2022 build output; long lines are inlined templates/metadata, not obfuscation. ai
source-diff obfuscated-file:fesm2022/agorapulse-ui-components-avatar-group.mjs AI (source-diff): Angular FESM2022 compiled output; long lines are normal Angular compiler metadata, not obfuscation. ai
phantom-deps phantom-dep:tslib AI (phantom-deps): tslib is a known implicit Angular/TypeScript runtime dependency; phantom-dep false positive for this package. ai

Versions (showing 51 of 85)

View all versions
Version Deps Published
20.4.25 1 / 0
20.4.24 1 / 0
20.4.23 1 / 0
20.4.22 1 / 0
20.4.21 1 / 0
20.4.20 1 / 0
20.4.19 1 / 0
20.4.18 1 / 0
20.4.17 1 / 0
20.4.16 1 / 0
20.4.15 1 / 0
20.4.14 1 / 0
20.4.13 1 / 0
20.4.12 1 / 0
20.4.11 1 / 0
20.4.10 1 / 0
20.4.9 1 / 0
20.4.8 1 / 0
20.4.7 1 / 0
20.4.6 1 / 0
20.4.5 1 / 0
20.4.4 1 / 0
20.4.3 1 / 0
20.4.2 1 / 0
20.4.1 1 / 0
20.4.0 1 / 0
20.3.48 1 / 0
20.3.47 1 / 0
20.3.46 1 / 0
20.3.45 1 / 0
20.3.44 1 / 0
20.3.43 1 / 0
20.3.42 1 / 0
20.3.41 1 / 0
20.3.40 1 / 0
20.3.39 1 / 0
20.3.38 1 / 0
20.3.37 1 / 0
20.3.36 1 / 0
20.3.35 1 / 0
20.3.34 1 / 0
20.3.33 1 / 0
20.3.32 1 / 0
20.3.31 1 / 0
20.3.29 1 / 0
20.3.28 1 / 0
20.3.25 1 / 0
20.3.24 1 / 0
20.3.23 1 / 0
20.3.22 1 / 0
20.3.21 1 / 0

v20.4.25

1 finding
LOW No provenance attestation provenance

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

v20.4.24

2 findings
HIGH New obfuscated file: fesm2022/agorapulse-ui-components-filter-chips-list.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.

v20.4.23

2 findings
HIGH New obfuscated file: fesm2022/agorapulse-ui-components-filter-chips-list.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.

v20.4.22

2 findings
HIGH New obfuscated file: fesm2022/agorapulse-ui-components-filter-chips-list.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.

v20.4.21

2 findings
HIGH New obfuscated file: fesm2022/agorapulse-ui-components-filter-chips-list.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.

v20.4.20

2 findings
HIGH New obfuscated file: fesm2022/agorapulse-ui-components-filter-chips-list.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.

v20.4.19

2 findings
HIGH New obfuscated file: fesm2022/agorapulse-ui-components-filter-chips-list.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.

v20.4.18

2 findings
HIGH New obfuscated file: fesm2022/agorapulse-ui-components-filter-chips-list.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.

v20.4.17

2 findings
HIGH New obfuscated file: fesm2022/agorapulse-ui-components-filter-chips-list.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.

v20.4.16

2 findings
HIGH New obfuscated file: fesm2022/agorapulse-ui-components-filter-chips-list.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.

v20.4.15

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.

v20.4.14

1 finding
LOW No provenance attestation provenance

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

v20.4.13

1 finding
LOW No provenance attestation provenance

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

v20.4.12

1 finding
LOW No provenance attestation provenance

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

v20.4.11

1 finding
LOW No provenance attestation provenance

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

v20.4.10

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.

v20.4.9

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.

v20.4.8

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.

v20.4.7

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.

v20.4.6

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.

v20.4.5

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.

v20.4.4

1 finding
LOW No provenance attestation provenance

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

v20.4.3

1 finding
LOW No provenance attestation provenance

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

v20.4.2

1 finding
LOW No provenance attestation provenance

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

v20.4.1

1 finding
LOW No provenance attestation provenance

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

v20.4.0

1 finding
LOW No provenance attestation provenance

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

v20.3.48

1 finding
LOW No provenance attestation provenance

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

v20.3.47

1 finding
LOW No provenance attestation provenance

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

v20.3.46

1 finding
LOW No provenance attestation provenance

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

v20.3.45

1 finding
LOW No provenance attestation provenance

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

v20.3.44

1 finding
LOW No provenance attestation provenance

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

v20.3.43

1 finding
LOW No provenance attestation provenance

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

v20.3.42

1 finding
LOW No provenance attestation provenance

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

v20.3.41

1 finding
LOW No provenance attestation provenance

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

v20.3.40

1 finding
LOW No provenance attestation provenance

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

v20.3.39

1 finding
LOW No provenance attestation provenance

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

v20.3.38

1 finding
LOW No provenance attestation provenance

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

v20.3.37

1 finding
LOW No provenance attestation provenance

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

v20.3.36

1 finding
LOW No provenance attestation provenance

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

v20.3.35

1 finding
LOW No provenance attestation provenance

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

v20.3.34

1 finding
LOW No provenance attestation provenance

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

v20.3.33

1 finding
LOW No provenance attestation provenance

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

v20.3.32

1 finding
LOW No provenance attestation provenance

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

v20.3.31

1 finding
LOW No provenance attestation provenance

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

v20.3.29

3 findings
HIGH Publisher changed: floppy → agorapulse-webmaster (on 2026-01-08) provenance

This version was published by a different npm account than previous versions on 2026-01-08. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: fesm2022/agorapulse-ui-components-avatar-group.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.

v20.3.28

1 finding
LOW No provenance attestation provenance

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

v20.3.25

1 finding
LOW No provenance attestation provenance

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

v20.3.24

1 finding
LOW No provenance attestation provenance

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

v20.3.23

1 finding
LOW No provenance attestation provenance

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

v20.3.22

1 finding
LOW No provenance attestation provenance

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

v20.3.21

3 findings
HIGH Publisher changed: floppy → agorapulse-webmaster (on 2025-12-02) provenance

This version was published by a different npm account than previous versions on 2025-12-02. This could indicate a legitimate maintainer transition or an account compromise.

HIGH New obfuscated file: fesm2022/agorapulse-ui-components-avatar-group.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.