@mseva/digit-ui-react-components
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 |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Change is 497 days stable on npm, not a takeover pattern; diff shows no material changes. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Weak metadata signals only; package has real inbound trust edges and unchanged content. | ai |
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 1.0.8 | 5 / 16 | |
| 1.0.6 | 5 / 16 | |
| 1.0.5 | 5 / 16 | |
| 1.0.4 | 5 / 16 | |
| 1.0.2 | 5 / 16 | |
| 1.0.1 | 5 / 16 | |
| 1.0.0 | 5 / 16 |
v1.0.2
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: anujsingh32.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.1
3 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: deepakmori.
This version was published by a different npm account (deepakmori) than the most recent previously approved version (anujsingh32) on 2025-03-07. It has since remained available on npm for 497 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.