@egovernments/digit-ui-module-hrms
HRMS
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:rooks | AI (phantom-deps): React hooks library used indirectly in UI module; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): React peer dependency; indirectly used in component rendering. | ai | |
| phantom-deps | phantom-dep:react-query | AI (phantom-deps): Data-fetching library used indirectly; stable for UI module pattern. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.9.10 | 8 / 0 | |
| 1.9.9 | 8 / 0 | |
| 1.9.8 | 8 / 0 | |
| 1.9.7 | 8 / 0 | |
| 1.9.6 | 8 / 0 | |
| 1.9.5 | 8 / 0 | |
| 1.9.4 | 8 / 0 | |
| 1.9.3 | 8 / 0 | |
| 1.9.2 | 8 / 0 | |
| 1.9.1 | 8 / 0 | |
| 1.9.0 | 8 / 0 | |
| 1.8.17 | 8 / 0 | |
| 1.8.16 | 8 / 0 | |
| 1.8.15 | 8 / 0 | |
| 1.8.14 | 8 / 0 | |
| 1.8.13 | 8 / 0 | |
| 1.7.40 | 8 / 0 |
v1.9.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.16
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.14
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.40
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.