@mseva/digit-ui-module-obps
Supply chain provenance
Status for the latest visible version.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| 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 100 of 140)
| 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 | |
| 1.1.45 | 14 / 0 | |
| 1.1.44 | 14 / 0 | |
| 1.1.43 | 14 / 0 | |
| 1.1.42 | 14 / 0 | |
| 1.1.41 | 14 / 0 | |
| 1.1.40 | 14 / 0 | |
| 1.1.39 | 14 / 0 | |
| 1.1.38 | 14 / 0 | |
| 1.1.37 | 14 / 0 | |
| 1.1.36 | 14 / 0 | |
| 1.1.35 | 14 / 0 | |
| 1.1.34 | 14 / 0 | |
| 1.1.33 | 14 / 0 | |
| 1.1.32 | 14 / 0 | |
| 1.1.31 | 14 / 0 | |
| 1.1.30 | 14 / 0 | |
| 1.1.29 | 14 / 0 | |
| 1.1.28 | 14 / 0 | |
| 1.1.27 | 14 / 0 | |
| 1.1.26 | 14 / 0 | |
| 1.1.25 | 14 / 0 | |
| 1.1.24 | 14 / 0 | |
| 1.1.23 | 14 / 0 | |
| 1.1.22 | 14 / 0 | |
| 1.1.21 | 14 / 0 | |
| 1.1.20 | 14 / 0 | |
| 1.1.19 | 14 / 0 | |
| 1.1.18 | 14 / 0 | |
| 1.1.17 | 14 / 0 | |
| 1.1.16 | 14 / 0 | |
| 1.1.15 | 14 / 0 | |
| 1.1.14 | 14 / 0 | |
| 1.1.13 | 14 / 0 | |
| 1.1.12 | 14 / 0 | |
| 1.1.11 | 14 / 0 | |
| 1.1.10 | 14 / 0 | |
| 1.1.9 | 14 / 0 | |
| 1.1.8 | 14 / 0 | |
| 1.1.7 | 14 / 0 | |
| 1.1.6 | 14 / 0 | |
| 1.1.5 | 14 / 0 | |
| 1.1.4 | 14 / 0 | |
| 1.1.3 | 14 / 0 | |
| 1.1.2 | 14 / 0 | |
| 1.1.0 | 14 / 0 | |
| 1.0.99 | 14 / 0 | |
| 1.0.98 | 14 / 0 | |
| 1.0.97 | 14 / 0 | |
| 1.0.96 | 14 / 0 |
v1.1.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.90
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.82
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.69
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.68
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.62
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.60
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.57
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.45
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (anou1234) than the most recent previously approved version (nayandhawan) on 2025-12-31, 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.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.42
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nayandhawan) than the most recent previously approved version (anou1234) on 2025-12-29, 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.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.36
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (anou1234) than the most recent previously approved version (nayandhawan) on 2025-12-22, 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.35
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nayandhawan) than the most recent previously approved version (anou1234) on 2025-12-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.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.31
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aashishgkpmg4) than the most recent previously approved version (nayandhawan) on 2025-12-18, but aashishgkpmg4 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.30
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nayandhawan) than the most recent previously approved version (aashishgkpmg4) on 2025-12-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.28
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nayandhawan) than the most recent previously approved version (aashishgkpmg4) on 2025-12-15, 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.27
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (aashishgkpmg4) than the most recent previously approved version (nayandhawan) on 2025-12-15, but aashishgkpmg4 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.26
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nayandhawan) than the most recent previously approved version (aashishgkpmg4) on 2025-12-15, 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.25
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.22
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nayandhawan) than the most recent previously approved version (aashishgkpmg4) on 2025-12-12, 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.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.9
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nayandhawan) than the most recent previously approved version (anujsingh32) on 2025-12-03, 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.8
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (nayandhawan) than the most recent previously approved version (anujsingh32) on 2025-12-03, 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.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (anujsingh32) than the most recent previously approved version (nayandhawan) on 2025-12-02, but anujsingh32 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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.97
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.