@mseva/digit-ui-module-noc
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Internal enterprise UI module; missing metadata is a hygiene issue, not a malice indicator across 133 versions. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): react-dom is a peer/build-time dep; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:redux-thunk | AI (phantom-deps): Stable false positive; redux-thunk used transitively in this UI module. | ai | |
| phantom-deps | phantom-dep:lodash.merge | AI (phantom-deps): Stable false positive; lodash.merge used in config/build context. | ai | |
| phantom-deps | phantom-dep:microbundle-crl | AI (phantom-deps): microbundle-crl is a build tool referenced in scripts; phantom-dep heuristic false positive. | ai |
Versions (showing 51 of 71)
| Version | Deps | Published |
|---|---|---|
| 1.0.89 | 14 / 0 | |
| 1.0.88 | 14 / 0 | |
| 1.0.87 | 14 / 0 | |
| 1.0.86 | 14 / 0 | |
| 1.0.85 | 14 / 0 | |
| 1.0.84 | 13 / 0 | |
| 1.0.83 | 13 / 0 | |
| 1.0.82 | 13 / 0 | |
| 1.0.81 | 13 / 0 | |
| 1.0.77 | 13 / 0 | |
| 1.0.74 | 13 / 0 | |
| 1.0.69 | 13 / 0 | |
| 1.0.68 | 13 / 0 | |
| 1.0.67 | 13 / 0 | |
| 1.0.66 | 13 / 0 | |
| 1.0.65 | 13 / 0 | |
| 1.0.64 | 13 / 0 | |
| 1.0.63 | 13 / 0 | |
| 1.0.62 | 13 / 0 | |
| 1.0.61 | 13 / 0 | |
| 1.0.59 | 13 / 0 | |
| 1.0.58 | 13 / 0 | |
| 1.0.57 | 13 / 0 | |
| 1.0.56 | 13 / 0 | |
| 1.0.55 | 13 / 0 | |
| 1.0.54 | 13 / 0 | |
| 1.0.53 | 13 / 0 | |
| 1.0.52 | 13 / 0 | |
| 1.0.51 | 13 / 0 | |
| 1.0.50 | 13 / 0 | |
| 1.0.49 | 13 / 0 | |
| 1.0.48 | 13 / 0 | |
| 1.0.47 | 13 / 0 | |
| 1.0.46 | 13 / 0 | |
| 1.0.42 | 13 / 0 | |
| 1.0.41 | 13 / 0 | |
| 1.0.40 | 13 / 0 | |
| 1.0.38 | 13 / 0 | |
| 1.0.37 | 13 / 0 | |
| 1.0.36 | 13 / 0 | |
| 1.0.35 | 13 / 0 | |
| 1.0.34 | 13 / 0 | |
| 1.0.32 | 13 / 0 | |
| 1.0.31 | 13 / 0 | |
| 1.0.30 | 13 / 0 | |
| 1.0.29 | 13 / 0 | |
| 1.0.28 | 13 / 0 | |
| 1.0.27 | 13 / 0 | |
| 1.0.26 | 13 / 0 | |
| 1.0.22 | 13 / 0 | |
| 1.0.21 | 13 / 0 |
v1.0.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.67
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.64
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.63
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.62
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.38
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-06, 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.0.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.34
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 (aashishgkpmg4) 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.0.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 (anujsingh32) than the most recent previously approved version (nayandhawan) on 2025-12-10, 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.0.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.29
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.