← Home

@mseva/digit-ui-module-obps

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

Maintainers

anou1234anujsingh32mdmujibalamnarinderkumar1aashishgkpmg4nayandhawanmujibalam2000saurabhsingh0001

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/index.modern.js AI (source-diff): Standard bundled React UI module; long lines are from bundler output, not obfuscation. ai
source-diff net-exec-file:dist/index.modern.js AI (source-diff): Network calls and dynamic patterns are from legitimate React/Redux/react-query usage in a UI module bundle. ai
source-diff source-size-tripled AI (source-diff): Size increase explained by addition of source maps (~16MB) and modern bundle format output. ai
phantom-deps phantom-dep:jspdf AI (phantom-deps): jspdf is a declared runtime dep used in build output; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:redux-thunk AI (phantom-deps): redux-thunk is a declared runtime dep; phantom-dep heuristic false positive for this package. ai
phantom-deps phantom-dep:microbundle-crl AI (phantom-deps): microbundle-crl is the build tool declared in scripts; not imported in source by design. ai

Versions (showing 51 of 140)

View all versions
Version Deps Published
1.2.5 15 / 0
1.2.3 15 / 0
1.2.0 14 / 0
1.1.94 14 / 0
1.1.93 14 / 0
1.1.92 14 / 0
1.1.91 14 / 0
1.1.90 14 / 0
1.1.89 14 / 0
1.1.88 14 / 0
1.1.87 14 / 0
1.1.86 14 / 0
1.1.85 14 / 0
1.1.84 14 / 0
1.1.82 14 / 0
1.1.81 14 / 0
1.1.80 14 / 0
1.1.79 14 / 0
1.1.78 14 / 0
1.1.77 14 / 0
1.1.76 14 / 0
1.1.75 14 / 0
1.1.74 14 / 0
1.1.73 14 / 0
1.1.72 14 / 0
1.1.71 14 / 0
1.1.70 14 / 0
1.1.69 14 / 0
1.1.68 14 / 0
1.1.67 14 / 0
1.1.66 14 / 0
1.1.65 14 / 0
1.1.64 14 / 0
1.1.63 14 / 0
1.1.62 14 / 0
1.1.61 14 / 0
1.1.60 14 / 0
1.1.59 14 / 0
1.1.58 14 / 0
1.1.57 14 / 0
1.1.56 14 / 0
1.1.55 14 / 0
1.1.54 14 / 0
1.1.53 14 / 0
1.1.52 14 / 0
1.1.51 14 / 0
1.1.50 14 / 0
1.1.49 14 / 0
1.1.48 14 / 0
1.1.47 14 / 0
1.1.46 14 / 0

v1.1.94

1 finding
LOW No provenance attestation provenance

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

v1.1.93

1 finding
LOW No provenance attestation provenance

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

v1.1.92

1 finding
LOW No provenance attestation provenance

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

v1.1.91

1 finding
LOW No provenance attestation provenance

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

v1.1.90

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mujibalam2000 → nayandhawan (on 2026-02-17, known maintainer) provenance

This version was published by a different npm account (nayandhawan) than the most recent previously approved version (mujibalam2000) on 2026-02-17, but nayandhawan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.87

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: anou1234 → nayandhawan (on 2026-02-11, known maintainer) provenance

This version was published by a different npm account (nayandhawan) than the most recent previously approved version (anou1234) on 2026-02-11, but nayandhawan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.85

1 finding
LOW No provenance attestation provenance

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

v1.1.84

1 finding
LOW No provenance attestation provenance

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

v1.1.82

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: anou1234 → mujibalam2000 (on 2026-02-09, known maintainer) provenance

This version was published by a different npm account (mujibalam2000) than the most recent previously approved version (anou1234) on 2026-02-09, but mujibalam2000 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.79

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: anou1234 → mujibalam2000 (on 2026-02-04, known maintainer) provenance

This version was published by a different npm account (mujibalam2000) than the most recent previously approved version (anou1234) on 2026-02-04, but mujibalam2000 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.78

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: nayandhawan → anou1234 (on 2026-02-04, known maintainer) provenance

This version was published by a different npm account (anou1234) than the most recent previously approved version (nayandhawan) on 2026-02-04, but anou1234 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.76

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mujibalam2000 → anou1234 (on 2026-02-04, known maintainer) provenance

This version was published by a different npm account (anou1234) than the most recent previously approved version (mujibalam2000) on 2026-02-04, but anou1234 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.75

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mujibalam2000 → anou1234 (on 2026-02-03, known maintainer) provenance

This version was published by a different npm account (anou1234) than the most recent previously approved version (mujibalam2000) on 2026-02-03, but anou1234 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.70

1 finding
LOW No provenance attestation provenance

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

v1.1.69

1 finding
LOW No provenance attestation provenance

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

v1.1.68

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mujibalam2000 → nayandhawan (on 2026-01-22, known maintainer) provenance

This version was published by a different npm account (nayandhawan) than the most recent previously approved version (mujibalam2000) on 2026-01-22, but nayandhawan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.67

1 finding
LOW No provenance attestation provenance

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

v1.1.65

1 finding
LOW No provenance attestation provenance

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

v1.1.64

1 finding
LOW No provenance attestation provenance

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

v1.1.63

1 finding
LOW No provenance attestation provenance

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

v1.1.62

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: nayandhawan → mujibalam2000 (on 2026-01-15, known maintainer) provenance

This version was published by a different npm account (mujibalam2000) than the most recent previously approved version (nayandhawan) on 2026-01-15, but mujibalam2000 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.61

1 finding
LOW No provenance attestation provenance

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

v1.1.60

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: anou1234 → nayandhawan (on 2026-01-13, known maintainer) provenance

This version was published by a different npm account (nayandhawan) than the most recent previously approved version (anou1234) on 2026-01-13, but nayandhawan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.59

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: anou1234 → mujibalam2000 (on 2026-01-09, known maintainer) provenance

This version was published by a different npm account (mujibalam2000) than the most recent previously approved version (anou1234) on 2026-01-09, but mujibalam2000 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.58

1 finding
LOW No provenance attestation provenance

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

v1.1.57

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mujibalam2000 → anou1234 (on 2026-01-07, known maintainer) provenance

This version was published by a different npm account (anou1234) than the most recent previously approved version (mujibalam2000) on 2026-01-07, but anou1234 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.56

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: anou1234 → mujibalam2000 (on 2026-01-06, known maintainer) provenance

This version was published by a different npm account (mujibalam2000) than the most recent previously approved version (anou1234) on 2026-01-06, but mujibalam2000 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.53

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mujibalam2000 → nayandhawan (on 2026-01-05, known maintainer) provenance

This version was published by a different npm account (nayandhawan) than the most recent previously approved version (mujibalam2000) on 2026-01-05, but nayandhawan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.51

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: nayandhawan → mujibalam2000 (on 2026-01-02, known maintainer) provenance

This version was published by a different npm account (mujibalam2000) than the most recent previously approved version (nayandhawan) on 2026-01-02, but mujibalam2000 is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.50

2 findings
LOW No provenance attestation provenance

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

INFO Publisher changed: mujibalam2000 → nayandhawan (on 2026-01-02, known maintainer) provenance

This version was published by a different npm account (nayandhawan) than the most recent previously approved version (mujibalam2000) on 2026-01-02, but nayandhawan is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.48

1 finding
LOW No provenance attestation provenance

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

v1.1.47

1 finding
LOW No provenance attestation provenance

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

v1.1.46

1 finding
LOW No provenance attestation provenance

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