← Home

@feedmepos/mf-mdm

A microfrontend package for device management in the FeedMe POS ecosystem.

14
Versions
UNLICENSED
License
No
Install Scripts
Missing
Provenance

Supply chain provenance

Status for the latest visible version.

No SLSA provenance npm registry signatures No source commit

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

victor.chailokingweidanielmcfluffy

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
source-diff obfuscated-file:dist/DeviceList-f33a8f32.js AI (source-diff): Standard Vite/Rollup minified bundle; readable Vue component code, not obfuscated malware. ai
source-diff obfuscated-file:dist/DeviceList-a1ba0d60.js AI (source-diff): Standard Vite/Rollup minified bundle output; readable imports confirm legitimate Vue app code, not malicious obfuscation. ai
source-diff obfuscated-file:dist/DeviceList-f33654a2.js AI (source-diff): Standard Vite minified ESM bundle; readable Vue/JS code in sample, not obfuscated. ai
source-diff obfuscated-file:dist/app-634f7d58.js AI (source-diff): Standard Vite minified ESM bundle; readable Vue/JS code in sample, not obfuscated. ai
dependencies unvetted-dep:xlsx AI (dependencies): xlsx is a widely-used spreadsheet library; addition is intentional and benign for this package. ai
dependencies unvetted-dep:@feedmepos/kitchen AI (dependencies): Same-org internal dependency; stable pattern for this package. ai
dependencies unvetted-dep:@feedmepos/core AI (dependencies): Same-org internal dependency; stable pattern for this package. ai
dependencies unvetted-dep:@feedmepos/ui-library AI (dependencies): Same-org internal dependency; stable pattern for this package. ai
dependencies unvetted-dep:@feedmepos/mdm-package AI (dependencies): Same-org internal dependency; stable pattern for this package. ai
dependencies unvetted-dep:@feedmepos/feature-flag AI (dependencies): Same-org internal dependency; stable pattern for this package. ai
phantom-deps phantom-dep:vue-i18n AI (phantom-deps): Config-file reference only; stable false positive for this package. ai
phantom-deps phantom-dep:firebase AI (phantom-deps): Config-file reference only; stable false positive for this package. ai
phantom-deps phantom-dep:@feedmepos/feature-flag AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages. ai
phantom-deps phantom-dep:@feedmepos/auth AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for monorepo packages. ai
phantom-deps phantom-dep:xlsx AI (phantom-deps): Config-file reference only; stable false positive for this build-tool package. ai
phantom-deps phantom-dep:change-case AI (phantom-deps): Config-file reference only; stable false positive for this package. ai

Versions (showing 14 of 14)

Version Deps Published
1.9.0 16 / 25
1.8.0 15 / 25
1.7.3 15 / 25
1.7.2 15 / 25
1.7.1 15 / 25
1.7.0 15 / 25
1.6.9 14 / 25
1.6.8 14 / 25
1.6.7 14 / 25
1.6.5 14 / 25
1.6.4 14 / 25
1.6.3 14 / 25
1.6.2 14 / 25
1.6.1 14 / 25

v1.9.0

3 findings
HIGH New obfuscated file: dist/app-634f7d58.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

HIGH New obfuscated file: dist/DeviceList-f33654a2.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.3

2 findings
HIGH New obfuscated file: dist/DeviceList-f33a8f32.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.7.1

2 findings
HIGH New obfuscated file: dist/DeviceList-a1ba0d60.js source-diff

Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.

LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.7.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.9

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.6.8

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.7

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.5

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.4

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.3

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.2

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.

v1.6.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.