@comet/cms-admin
Comet CMS 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/form/file/chooseFile/BaseChooseDamFileDialog.js | AI (source-diff): Standard Babel CJS output; long lines from compiled React components, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:lib/form/file/chooseFile/ChooseDamFileDialog.js | AI (source-diff): Standard Babel CJS output; long lines from compiled React components, not malicious obfuscation. | ai | |
| source-diff | obfuscated-file:lib/blocks/table/CellValue.js | AI (source-diff): Babel-compiled CommonJS output with emotion/MUI helpers; long lines are inlined Babel runtime polyfills, not obfuscation. | ai | |
| source-diff | obfuscated-file:lib/blocks/table/ColumnHeader.js | AI (source-diff): Same Babel compilation pattern; _slicedToArray and similar helpers are standard Babel output. | ai | |
| source-diff | obfuscated-file:lib/blocks/table/EditCell.js | AI (source-diff): Same Babel compilation pattern; no suspicious network or credential-access code present. | ai | |
| phantom-deps | phantom-dep:lodash.set | AI (phantom-deps): Stable false positive for compiled TS package. | ai | |
| phantom-deps | phantom-dep:prop-types | AI (phantom-deps): Stable false positive for compiled TS package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Template literal uses __dirname to resolve a fixed sibling path in a CLI bin script — not user-controlled input. | ai | |
| phantom-deps | phantom-dep:@comet/admin-theme | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic fires on compiled TS monorepo packages. | ai | |
| phantom-deps | phantom-dep:@graphql-typed-document-node/core | AI (phantom-deps): Stable false positive for compiled TS package with generated types. | ai | |
| phantom-deps | phantom-dep:lodash.clonedeep | AI (phantom-deps): Stable false positive for compiled TS package. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): Used in build scripts, not runtime imports; stable false positive for this compiled TS package. | ai | |
| phantom-deps | phantom-dep:@mui/lab | AI (phantom-deps): Peer/dev dep used in compiled output; phantom-dep heuristic fires on compiled TS packages. | ai | |
| phantom-deps | phantom-dep:split.js | AI (phantom-deps): Stable false positive for compiled TS package. | ai | |
| phantom-deps | phantom-dep:lodash.get | AI (phantom-deps): Stable false positive for compiled TS package. | ai |
Versions (showing 42 of 42)
| Version | Deps | Published |
|---|---|---|
| 8.24.0 | 31 / 55 | |
| 8.23.4 | 31 / 55 | |
| 8.23.3 | 31 / 55 | |
| 8.23.2 | 31 / 55 | |
| 8.23.1 | 31 / 55 | |
| 8.23.0 | 31 / 55 | |
| 8.22.0 | 31 / 55 | |
| 8.21.1 | 31 / 55 | |
| 8.21.0 | 31 / 55 | |
| 8.20.4 | 31 / 55 | |
| 8.20.3 | 31 / 55 | |
| 8.20.0 | 31 / 55 | |
| 8.19.0 | 29 / 51 | |
| 8.18.0 | 29 / 51 | |
| 8.17.1 | 29 / 51 | |
| 8.17.0 | 29 / 51 | |
| 8.16.0 | 29 / 51 | |
| 8.15.0 | 29 / 51 | |
| 8.14.0 | 29 / 48 | |
| 8.13.0 | 29 / 48 | |
| 8.12.0 | 29 / 48 | |
| 8.11.1 | 29 / 48 | |
| 8.11.0 | 29 / 48 | |
| 8.10.0 | 29 / 52 | |
| 8.9.0 | 30 / 53 | |
| 8.8.0 | 30 / 53 | |
| 8.7.1 | 30 / 54 | |
| 8.7.0 | 30 / 54 | |
| 8.6.0 | 30 / 54 | |
| 8.5.2 | 30 / 54 | |
| 8.5.1 | 30 / 54 | |
| 8.5.0 | 30 / 54 | |
| 8.4.2 | 30 / 54 | |
| 8.4.0 | 30 / 54 | |
| 8.3.0 | 30 / 54 | |
| 8.2.0 | 30 / 54 | |
| 8.1.1 | 30 / 54 | |
| 8.1.0 | 30 / 54 | |
| 8.0.0 | 31 / 54 | |
| 7.25.14 | 44 / 62 | |
| 7.25.13 | 44 / 62 | |
| 7.25.12 | 44 / 62 |
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
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 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.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. Consider requesting the maintainer enable provenance via CI/CD.
v8.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.20.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.20.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.20.0
4 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.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.19.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.11.0
1 findingPackage 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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.