@murumets-ee/notifications

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

ranx2k

Accepted risks

Findings the reviewer chose to accept rather than block on.

Source	Rule	Reason	Accepted by	When
source-diff	obfuscated-file:dist/email-DNqSm5nL.mjs	AI (source-diff): Standard tsdown minified ESM output; content is readable email-channel notification logic.	ai	2026/05/26
source-diff	obfuscated-file:dist/client-BxbxSR5Y.mjs	AI (source-diff): Minified ESM bundle from tsdown build; content is readable notification logic, not obfuscated malware.	ai	2026/05/22
source-diff	obfuscated-file:dist/email-DBcpOgwr.mjs	AI (source-diff): Minified ESM bundle from tsdown build; content is readable email channel logic, not obfuscated malware.	ai	2026/05/22
phantom-deps	phantom-dep:@murumets-ee/auth	AI (phantom-deps): Same-org scoped package; likely monorepo internal dependency pattern.	ai	2026/05/18
phantom-deps	phantom-dep:@murumets-ee/logging	AI (phantom-deps): Same-org scoped package; likely monorepo internal dependency pattern.	ai	2026/05/18
bogus-package	bogus-package	AI (bogus-package): Internal org package; missing metadata typical for monorepo modules.	ai	2026/05/18

Versions (showing 32 of 32)

Version	Deps	Published
0.25.0	9 / 4	2026-05-29
0.24.1	9 / 4	2026-05-29
0.24.0	9 / 4	2026-05-29
0.23.2	9 / 4	2026-05-24
0.23.1	9 / 4	2026-05-23
0.23.0	9 / 4	2026-05-23
0.22.1	9 / 4	2026-05-22
0.22.0	9 / 4	2026-05-22
0.21.1	9 / 4	2026-05-21
0.21.0	9 / 4	2026-05-21
0.20.0	9 / 4	2026-05-20
0.19.0	9 / 4	2026-05-14
0.18.0	9 / 4	2026-05-14
0.17.1	9 / 4	2026-05-13
0.17.0	9 / 4	2026-05-13
0.16.5	9 / 4	2026-05-13
0.16.4	9 / 4	2026-05-13
0.16.3	9 / 4	2026-05-13
0.16.2	9 / 4	2026-05-13
0.16.1	9 / 4	2026-05-12
0.16.0	9 / 4	2026-05-12
0.15.4	9 / 4	2026-05-12
0.15.3	9 / 4	2026-05-12
0.15.2	9 / 4	2026-05-12
0.15.1	9 / 4	2026-05-12
0.15.0	9 / 4	2026-05-11
0.14.0	9 / 4	2026-05-11
0.13.3	9 / 4	2026-05-10
0.13.2	9 / 4	2026-05-10
0.13.1	9 / 4	2026-05-08
0.13.0	9 / 4	2026-05-08
0.12.0	9 / 4	2026-05-05

v0.25.0

1 finding

LOW No provenance attestation provenance

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

v0.24.1

1 finding

LOW No provenance attestation provenance

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

v0.24.0

1 finding

LOW No provenance attestation provenance

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

v0.23.2

1 finding

LOW No provenance attestation provenance

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

v0.23.1

1 finding

LOW No provenance attestation provenance

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

v0.23.0

1 finding

LOW No provenance attestation provenance

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

v0.22.1

1 finding

LOW No provenance attestation provenance

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

v0.22.0

1 finding

LOW No provenance attestation provenance

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

v0.21.1

3 findings

HIGH New obfuscated file: dist/client-BxbxSR5Y.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.

HIGH New obfuscated file: dist/email-DBcpOgwr.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.

v0.21.0

3 findings

HIGH New obfuscated file: dist/client-BxbxSR5Y.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.

HIGH New obfuscated file: dist/email-DNqSm5nL.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.

v0.20.0

3 findings

HIGH New obfuscated file: dist/client-BxbxSR5Y.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.

HIGH New obfuscated file: dist/email-DNqSm5nL.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.

v0.19.0

1 finding

LOW No provenance attestation provenance

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

v0.18.0

1 finding

LOW No provenance attestation provenance

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

v0.17.1

1 finding

LOW No provenance attestation provenance

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

v0.17.0

1 finding

LOW No provenance attestation provenance

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

v0.16.5

1 finding

LOW No provenance attestation provenance

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

v0.16.4

1 finding

LOW No provenance attestation provenance

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

v0.16.3

1 finding

LOW No provenance attestation provenance

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

v0.16.2

1 finding

LOW No provenance attestation provenance

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

v0.16.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.

v0.16.0

1 finding

LOW No provenance attestation provenance

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

v0.15.4

1 finding

LOW No provenance attestation provenance

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

v0.15.3

1 finding

LOW No provenance attestation provenance

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

v0.15.2

1 finding

LOW No provenance attestation provenance

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

v0.15.1

1 finding

LOW No provenance attestation provenance

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

v0.15.0

1 finding

LOW No provenance attestation provenance

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

v0.14.0

1 finding

LOW No provenance attestation provenance

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

v0.13.3

1 finding

LOW No provenance attestation provenance

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

v0.13.2

1 finding

LOW No provenance attestation provenance

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

v0.13.1

1 finding

LOW No provenance attestation provenance

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

v0.13.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.12.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.