@everymatrix/pam-change-password

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

clokzeoleksandr.v.stepanovtaras.maksymivnatalya.anisimovaemfe_releasemariana.gheorgheadrian.priponandriizadvirnyiraulvasileemstrulea.sebastianstefan.vladgoe.sutadragos.bodeamaria.bumbarstefanaotong.woodtikarncatalinpoclidcristi.ungureanuliviuclement.everymatrixmihaibalanfrankie24

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/esm/pam-change-password-259289fa.js	AI (source-diff): Standard Stencil.js minified build artifact; content is UI translations and component logic only.	ai	2026/04/30
source-diff	obfuscated-file:dist/pam-change-password/pam-change-password-259289fa.js	AI (source-diff): Standard Stencil.js minified build artifact; content is UI translations and component logic only.	ai	2026/04/30
source-diff	obfuscated-file:dist/cjs/pam-change-password-6ab9b8bd.js	AI (source-diff): Standard Stencil.js minified build artifact; content is UI translations and component logic only.	ai	2026/04/30
bogus-package	bogus-package	AI (bogus-package): Established scoped monorepo component family with 292 versions; sparse metadata is a consistent pattern across all releases.	ai	2026/04/29
npm-metadata	no-description	AI (npm-metadata): Consistent across all @everymatrix component packages; not a malware indicator here.	ai	2026/04/29
provenance	no-provenance	AI (provenance): No provenance is consistent across this package family; not a risk signal here.	ai	2026/04/29

Versions (showing 2 of 213)

Version	Deps	Published
1.67.3	0 / 0	2025-05-11
1.67.0	0 / 0	2025-05-07

v1.67.3

1 finding

INFO No provenance attestation provenance

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

v1.67.0

1 finding

INFO No provenance attestation provenance

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