@sasindi/manage-location
An OpenMRS seed application for building microfrontends
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:lodash-es | AI (phantom-deps): lodash-es is a common utility; phantom-dep heuristic fires on config references, not a real risk for this package. | ai | |
| phantom-deps | phantom-dep:sweetalert2 | AI (phantom-deps): sweetalert2 is a well-known UI library; phantom-dep heuristic fires on config references. | ai | |
| phantom-deps | phantom-dep:@carbon/react | AI (phantom-deps): @carbon/react is IBM's design system; phantom-dep heuristic fires on config references. | ai | |
| phantom-deps | phantom-dep:sweetalert2-react-content | AI (phantom-deps): sweetalert2-react-content is a known React wrapper; phantom-dep heuristic fires on config references. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.0.12 | 4 / 46 | |
| 1.0.11 | 4 / 46 | |
| 1.0.10 | 4 / 46 | |
| 1.0.9 | 4 / 46 | |
| 1.0.8 | 4 / 46 | |
| 1.0.7 | 4 / 46 | |
| 1.0.5 | 4 / 46 | |
| 1.0.4 | 4 / 46 | |
| 1.0.3 | 4 / 46 | |
| 1.0.2 | 4 / 46 | |
| 1.0.1 | 4 / 46 | |
| 1.0.0 | 4 / 46 |
v1.0.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.