@nuskin/nextgen-header
Header micro-frontend and npm component library
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:package-dist/index.mjs | AI (source-diff): Standard webpack bundle of MUI/emotion/react; long lines are minified but not obfuscated malware. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase explained by bundling MUI and emotion into package-dist; expected for a component library. | ai | |
| source-diff | net-exec-file:package-dist/index.mjs | AI (source-diff): Network calls and dynamic execution are part of normal React/MUI component library bundle, not dropper behavior. | ai | |
| phantom-deps | phantom-dep:@mui/base | AI (phantom-deps): Referenced in config/webpack files; bundled library pattern, not a real phantom dep. | ai | |
| phantom-deps | phantom-dep:@nuskin/foundation-ui-components | AI (phantom-deps): Same-org dependency for UI; stable for this package. | ai | |
| phantom-deps | phantom-dep:jest-environment-jsdom | AI (phantom-deps): Jest config; referenced in config files. | ai | |
| phantom-deps | phantom-dep:@nuskin/foundation-theme | AI (phantom-deps): Same-org dependency; used in library code. | ai | |
| phantom-deps | phantom-dep:core-js | AI (phantom-deps): Runtime polyfill; implicit dependency via Babel/webpack transpilation. | ai | |
| phantom-deps | phantom-dep:@mui/material | AI (phantom-deps): UI library dependency; referenced in config. | ai | |
| phantom-deps | phantom-dep:@mui/icons-material | AI (phantom-deps): MUI icons dependency; referenced in config. | ai | |
| phantom-deps | phantom-dep:@emotion/styled | AI (phantom-deps): Styling dependency; referenced in config. | ai | |
| phantom-deps | phantom-dep:@loadable/server | AI (phantom-deps): Code-splitting library; referenced in server config. | ai | |
| phantom-deps | phantom-dep:@loadable/component | AI (phantom-deps): Code-splitting library; referenced in config. | ai | |
| phantom-deps | phantom-dep:@loadable/babel-plugin | AI (phantom-deps): Babel plugin; referenced in build config. | ai | |
| phantom-deps | phantom-dep:contentstack | AI (phantom-deps): CMS dependency; referenced in config. | ai | |
| phantom-deps | phantom-dep:@contentstack/delivery-sdk | AI (phantom-deps): CMS SDK; referenced in config. | ai | |
| phantom-deps | phantom-dep:@contentstack/utils | AI (phantom-deps): CMS utility; referenced in config. | ai | |
| phantom-deps | phantom-dep:@contentstack/live-preview-utils | AI (phantom-deps): CMS utility; referenced in config. | ai | |
| phantom-deps | phantom-dep:react-gtm-module | AI (phantom-deps): Analytics dependency; referenced in config. | ai | |
| phantom-deps | phantom-dep:eslint-config-next | AI (phantom-deps): ESLint config; referenced in .eslintrc. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-prettier | AI (phantom-deps): ESLint plugin; referenced in config. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-spellcheck | AI (phantom-deps): ESLint plugin; referenced in config. | ai | |
| phantom-deps | phantom-dep:eslint-plugin-unused-imports | AI (phantom-deps): ESLint plugin; referenced in config. | ai | |
| phantom-deps | phantom-dep:react-dom | AI (phantom-deps): Peer dependency; implicitly required by React component library. | ai | |
| phantom-deps | phantom-dep:express | AI (phantom-deps): Server-side rendering dependency; referenced in server config. | ai | |
| phantom-deps | phantom-dep:regenerator-runtime | AI (phantom-deps): Runtime polyfill; implicit dependency via Babel transpilation. | ai | |
| phantom-deps | phantom-dep:@mui/system | AI (phantom-deps): Transitive MUI dependency; referenced in config. | ai | |
| phantom-deps | phantom-dep:cross-env | AI (phantom-deps): Build script utility; stable for this build-tool package. | ai | |
| phantom-deps | phantom-dep:dotenv | AI (phantom-deps): Config management referenced in build; stable for this package. | ai | |
| phantom-deps | phantom-dep:jest | AI (phantom-deps): Test framework referenced in config; stable for this build-tool package. | ai | |
| phantom-deps | phantom-dep:eslint | AI (phantom-deps): Linter referenced in config; stable for this build-tool package. | ai | |
| phantom-deps | phantom-dep:prettier | AI (phantom-deps): Formatter referenced in config; stable for this build-tool package. | ai |
Versions (showing 48 of 48)
| Version | Deps | Published |
|---|---|---|
| 1.41.0 | 30 / 37 | |
| 1.40.0 | 30 / 37 | |
| 1.39.1 | 30 / 37 | |
| 1.39.0 | 30 / 37 | |
| 1.38.0 | 30 / 37 | |
| 1.37.0 | 30 / 37 | |
| 1.36.0 | 30 / 37 | |
| 1.35.0 | 30 / 37 | |
| 1.34.0 | 30 / 37 | |
| 1.33.0 | 30 / 37 | |
| 1.32.0 | 30 / 37 | |
| 1.31.0 | 30 / 37 | |
| 1.30.0 | 30 / 37 | |
| 1.29.1 | 29 / 37 | |
| 1.29.0 | 29 / 37 | |
| 1.28.1 | 29 / 37 | |
| 1.28.0 | 29 / 37 | |
| 1.27.0 | 29 / 37 | |
| 1.26.0 | 32 / 38 | |
| 1.25.0 | 32 / 38 | |
| 1.24.0 | 32 / 38 | |
| 1.23.1 | 32 / 38 | |
| 1.23.0 | 32 / 38 | |
| 1.22.0 | 32 / 38 | |
| 1.21.0 | 32 / 38 | |
| 1.20.0 | 32 / 38 | |
| 1.19.0 | 32 / 38 | |
| 1.18.0 | 31 / 38 | |
| 1.17.0 | 31 / 38 | |
| 1.16.1 | 31 / 38 | |
| 1.16.0 | 31 / 38 | |
| 1.15.0 | 31 / 38 | |
| 1.14.0 | 32 / 38 | |
| 1.13.0 | 32 / 38 | |
| 1.12.0 | 31 / 38 | |
| 1.11.0 | 31 / 38 | |
| 1.10.0 | 31 / 38 | |
| 1.9.0 | 31 / 38 | |
| 1.8.0 | 31 / 38 | |
| 1.7.0 | 31 / 38 | |
| 1.6.1 | 31 / 38 | |
| 1.6.0 | 31 / 38 | |
| 1.5.0 | 31 / 38 | |
| 1.4.0 | 31 / 38 | |
| 1.3.0 | 31 / 38 | |
| 1.2.0 | 31 / 38 | |
| 1.1.0 | 28 / 34 | |
| 1.0.0 | 26 / 34 |
v1.41.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.40.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.39.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.37.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.36.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.35.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.34.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.33.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.32.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.31.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.30.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.29.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.28.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.27.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.26.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.5.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
3 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
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.