@comet/admin
Comet Admin package
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 |
|---|---|---|---|---|
| source-diff | obfuscated-file:lib/mui/menu/Menu.styles.d.ts | AI (source-diff): TypeScript declaration file with long union types from MUI prop forwarding; not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/mui/menu/Item.styles.js | AI (source-diff): Babel-compiled tagged template literal CSS-in-JS; long lines are normal for this build output pattern. | ai | |
| source-diff | obfuscated-file:lib/mui/menu/CollapsibleItem.styles.d.ts | AI (source-diff): TypeScript declaration file with long union types from MUI prop forwarding; not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/mui/menu/Item.styles.d.ts | AI (source-diff): TypeScript declaration file with long union types from MUI prop forwarding; not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/fullPageAlert/FullPageAlert.styles.d.ts | AI (source-diff): Long lines in .d.ts files are a TypeScript artifact from MUI styled-component type emission, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/common/buttons/helpDialogButton/HelpDialogButton.sc.d.ts | AI (source-diff): Long lines in .d.ts files are caused by deeply nested MUI/React generic types, not obfuscation. Stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@comet/admin-theme | AI (phantom-deps): Same-org sibling package; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@mui/private-theming | AI (phantom-deps): Referenced in config files only; stable false positive for this package. | ai |
Versions (showing 44 of 44)
| Version | Deps | Published |
|---|---|---|
| 8.24.0 | 14 / 54 | |
| 8.23.4 | 14 / 54 | |
| 8.23.3 | 14 / 54 | |
| 8.23.2 | 14 / 54 | |
| 8.23.1 | 14 / 54 | |
| 8.23.0 | 14 / 54 | |
| 8.22.0 | 14 / 54 | |
| 8.21.1 | 14 / 54 | |
| 8.21.0 | 14 / 54 | |
| 8.20.4 | 14 / 54 | |
| 8.20.3 | 14 / 54 | |
| 8.20.2 | 14 / 54 | |
| 8.20.1 | 14 / 54 | |
| 8.20.0 | 14 / 54 | |
| 8.19.0 | 14 / 54 | |
| 8.18.0 | 14 / 54 | |
| 8.17.1 | 14 / 54 | |
| 8.17.0 | 14 / 54 | |
| 8.16.0 | 14 / 54 | |
| 8.15.0 | 14 / 54 | |
| 8.14.0 | 14 / 52 | |
| 8.13.0 | 14 / 52 | |
| 8.12.0 | 14 / 52 | |
| 8.11.1 | 14 / 52 | |
| 8.11.0 | 14 / 52 | |
| 8.10.0 | 14 / 55 | |
| 8.9.0 | 14 / 55 | |
| 8.8.0 | 14 / 55 | |
| 8.7.1 | 14 / 55 | |
| 8.7.0 | 14 / 55 | |
| 8.6.0 | 14 / 55 | |
| 8.5.2 | 14 / 48 | |
| 8.5.1 | 14 / 48 | |
| 8.5.0 | 14 / 48 | |
| 8.4.2 | 14 / 48 | |
| 8.4.0 | 14 / 48 | |
| 8.3.0 | 14 / 48 | |
| 8.2.0 | 14 / 48 | |
| 8.1.1 | 14 / 48 | |
| 8.1.0 | 14 / 48 | |
| 8.0.0 | 14 / 47 | |
| 7.25.14 | 15 / 49 | |
| 7.25.13 | 15 / 49 | |
| 7.25.12 | 15 / 49 |
v8.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.23.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.23.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.23.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.23.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.23.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.22.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.20.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.20.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.19.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.17.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.17.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.16.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.14.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.13.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.5.1
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.2
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
2 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.14
5 findingsNewly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Newly added source file contains lines over 3000 chars, suggesting minified or obfuscated code. New obfuscated files are a strong attack indicator.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.25.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.25.12
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.