@feedmepos/mf-hrm-portal
A Vue 3 + TypeScript Human Resource Management portal application built as a microfrontend. This application provides comprehensive HR management features including employee management, role management, team management, and timesheet tracking.
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Bundled micro-frontend; deps declared for consumers, not necessarily directly imported in analyzed files. | ai | |
| phantom-deps | phantom-dep:xlsx | AI (phantom-deps): Same bundled micro-frontend pattern; declared for consumer use. | ai | |
| phantom-deps | phantom-dep:dayjs | AI (phantom-deps): Same bundled micro-frontend pattern. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Same bundled micro-frontend pattern. | ai | |
| phantom-deps | phantom-dep:vue3-lottie | AI (phantom-deps): Same bundled micro-frontend pattern. | ai | |
| phantom-deps | phantom-dep:@feedmepos/auth | AI (phantom-deps): Same org scope; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:libphonenumber-js | AI (phantom-deps): Same bundled micro-frontend pattern. | ai | |
| phantom-deps | phantom-dep:@feedmepos/feature-flag | AI (phantom-deps): Same org scope; stable false positive for this package. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 2.0.10 | 16 / 34 | |
| 2.0.8 | 16 / 34 | |
| 2.0.7 | 16 / 34 | |
| 1.0.1 | 14 / 31 |
v2.0.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.8
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.