← Home

moment-jalaali

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

Maintainers

behrangalitaheri

Keywords

jalaalijalalipersiankhorshidishamsidatecalendarconversionconvert

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
phantom-deps phantom-dep:moment-timezone AI (phantom-deps): Likely used in UMD build step, not directly imported in source. ai
source-diff obfuscated-file:bower_components/momentjs/min/lang/ar.js AI (source-diff): Minified vendored moment.js locale file, not injected obfuscation. ai
source-diff obfuscated-file:bower_components/momentjs/min/lang/cv.js AI (source-diff): Minified vendored moment.js locale file, not injected obfuscation. ai
vendored-integrity unresolved-vendored-tree:bower_components/momentjs AI (vendored-integrity): Legitimate bower-vendored moment.js dependency bundled for browser use. ai
semgrep semgrep:dynamic-require AI (semgrep): Standard moment.js locale-loading pattern, local path only. ai
source-diff obfuscated-file:bower_components/momentjs/min/lang/uk.js AI (source-diff): Minified vendored moment.js locale file, not injected obfuscation. ai
source-diff obfuscated-file:bower_components/momentjs/min/lang/ru.js AI (source-diff): Minified vendored moment.js locale file, not injected obfuscation. ai
source-diff obfuscated-file:bower_components/momentjs/min/lang/ka.js AI (source-diff): Minified vendored moment.js locale file, not injected obfuscation. ai
source-diff obfuscated-file:bower_components/momentjs/min/lang/el.js AI (source-diff): Minified vendored moment.js locale file, not injected obfuscation. ai
source-diff obfuscated-file:bower_components/momentjs/min/lang/ne.js AI (source-diff): Minified vendored moment.js locale file, not injected obfuscation. ai
source-diff obfuscated-file:bower_components/momentjs/min/lang/fa.js AI (source-diff): Minified vendored moment.js locale file, not injected obfuscation. ai
source-diff obfuscated-file:bower_components/momentjs/min/lang/th.js AI (source-diff): Minified vendored moment.js locale file, not injected obfuscation. ai
publish-pattern dormant-publish AI (publish-pattern): Same long-time publisher, no behavior change; dormancy alone isn't malicious. ai
phantom-deps phantom-dep:rimraf AI (phantom-deps): rimraf used only in clean script, not imported; standard build tooling. ai
provenance publisher-changed-stale AI (provenance): Long-standing publisher change with no takedown; publisher has clean track record. ai

Versions (showing 43 of 43)

Version Deps Published
0.10.4 3 / 4
0.10.3 4 / 3
0.10.2 4 / 3
0.10.1 4 / 3
0.10.0 4 / 3
0.9.6 4 / 3
0.9.5 4 / 3
0.9.4 4 / 3
0.9.3 4 / 3
0.9.2 4 / 3
0.9.1 4 / 3
0.9.0 4 / 3
0.8.3 4 / 3
0.8.2 4 / 3
0.8.1 4 / 3
0.8.0 4 / 3
0.7.4 3 / 3
0.7.3 3 / 3
0.7.2 3 / 3
0.7.1 3 / 3
0.7.0 3 / 3
0.6.1 2 / 5
0.6.0 2 / 5
0.5.1 2 / 5
0.4.0 2 / 5
0.3.8 2 / 5
0.3.6 2 / 4
0.3.4 2 / 4
0.3.3 2 / 4
0.3.2 2 / 4
0.3.0 2 / 4
0.2.3 1 / 4
0.2.2 1 / 4
0.2.1 1 / 4
0.2.0 1 / 4
0.1.9 1 / 9
0.1.8 1 / 9
0.1.7 1 / 9
0.1.6 1 / 9
0.1.5 1 / 11
0.1.2 1 / 10
0.1.1 1 / 10
0.1.0 1 / 9

v0.10.3

1 finding
LOW No provenance attestation provenance

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

v0.10.2

1 finding
LOW No provenance attestation provenance

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

v0.10.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.10.0

1 finding
LOW No provenance attestation provenance

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

v0.9.6

1 finding
LOW No provenance attestation provenance

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

v0.9.5

1 finding
LOW No provenance attestation provenance

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

v0.9.4

1 finding
LOW No provenance attestation provenance

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

v0.9.3

1 finding
LOW No provenance attestation provenance

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

v0.9.2

1 finding
LOW No provenance attestation provenance

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

v0.9.1

1 finding
LOW No provenance attestation provenance

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

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.8.3

1 finding
LOW No provenance attestation provenance

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

v0.8.2

1 finding
LOW No provenance attestation provenance

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

v0.8.1

1 finding
LOW No provenance attestation provenance

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

v0.8.0

1 finding
LOW No provenance attestation provenance

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

v0.7.4

1 finding
LOW No provenance attestation provenance

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

v0.7.3

2 findings
MEDIUM Publisher changed: behrang → alitaheri (on 2018-05-09, unremoved on npm for 2999d) provenance

This version was published by a different npm account (alitaheri) than the most recent previously approved version (behrang) on 2018-05-09. It has since remained available on npm for 2999 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.7.2

2 findings
MEDIUM Publisher changed: behrang → alitaheri (on 2017-09-03, unremoved on npm for 3247d) provenance

This version was published by a different npm account (alitaheri) than the most recent previously approved version (behrang) on 2017-09-03. It has since remained available on npm for 3247 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.7.1

2 findings
MEDIUM Publisher changed: behrang → alitaheri (on 2017-08-25, unremoved on npm for 3256d) provenance

This version was published by a different npm account (alitaheri) than the most recent previously approved version (behrang) on 2017-08-25. It has since remained available on npm for 3256 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.7.0

2 findings
MEDIUM Publisher changed: behrang → alitaheri (on 2017-06-27, unremoved on npm for 3315d) provenance

This version was published by a different npm account (alitaheri) than the most recent previously approved version (behrang) on 2017-06-27. It has since remained available on npm for 3315 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.

LOW No provenance attestation provenance

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

v0.6.1

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.1

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.8

1 finding
LOW No provenance attestation provenance

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

v0.3.6

1 finding
LOW No provenance attestation provenance

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

v0.3.4

1 finding
LOW No provenance attestation provenance

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

v0.3.3

1 finding
LOW No provenance attestation provenance

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

v0.3.2

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.3

1 finding
LOW No provenance attestation provenance

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

v0.2.2

1 finding
LOW No provenance attestation provenance

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

v0.2.1

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

v0.1.9

1 finding
LOW No provenance attestation provenance

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

v0.1.8

1 finding
LOW No provenance attestation provenance

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

v0.1.7

1 finding
LOW No provenance attestation provenance

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

v0.1.6

1 finding
LOW No provenance attestation provenance

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

v0.1.5

10 findings
HIGH New obfuscated file: bower_components/momentjs/min/lang/uk.js 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: bower_components/momentjs/min/lang/ru.js 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: bower_components/momentjs/min/lang/ka.js 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: bower_components/momentjs/min/lang/el.js 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: bower_components/momentjs/min/lang/ar.js 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: bower_components/momentjs/min/lang/ne.js 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: bower_components/momentjs/min/lang/fa.js 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: bower_components/momentjs/min/lang/th.js 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: bower_components/momentjs/min/lang/cv.js 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.1.2

1 finding
LOW No provenance attestation provenance

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

v0.1.1

1 finding
LOW No provenance attestation provenance

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

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