@comet/brevo-admin
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Large version jump reflects monorepo release cadence, not account takeover. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): New deps are sibling @comet/* packages from the same monorepo at the same version. | ai | |
| dependencies | unvetted-dep:@comet/admin | AI (dependencies): Sibling package from same vivid-planet/comet monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@comet/cms-admin | AI (dependencies): Sibling package from same vivid-planet/comet monorepo; stable false positive. | ai | |
| dependencies | unvetted-dep:@comet/admin-date-time | AI (dependencies): Sibling package from same vivid-planet/comet monorepo; stable false positive. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 8.24.0 | 7 / 35 | |
| 8.23.4 | 7 / 35 | |
| 8.23.3 | 7 / 35 | |
| 8.23.2 | 7 / 35 | |
| 8.23.1 | 7 / 35 | |
| 8.23.0 | 7 / 35 | |
| 8.22.0 | 7 / 35 | |
| 8.21.1 | 7 / 35 | |
| 8.21.0 | 7 / 35 | |
| 8.20.4 | 7 / 35 | |
| 8.20.3 | 7 / 35 | |
| 8.20.2 | 7 / 35 | |
| 8.20.1 | 7 / 35 | |
| 8.20.0 | 7 / 35 | |
| 8.19.0 | 7 / 35 | |
| 8.18.0 | 7 / 35 | |
| 8.17.1 | 7 / 35 | |
| 8.17.0 | 7 / 35 | |
| 8.16.0 | 7 / 35 | |
| 8.15.0 | 7 / 35 | |
| 8.14.0 | 7 / 35 | |
| 8.13.0 | 7 / 35 | |
| 8.12.0 | 7 / 35 | |
| 3.2.1 | 4 / 38 | |
| 3.2.0 | 4 / 38 | |
| 3.1.5 | 4 / 38 | |
| 3.1.4 | 4 / 38 | |
| 3.1.3 | 4 / 38 | |
| 3.1.2 | 4 / 38 | |
| 3.1.1 | 4 / 38 |
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. 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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v8.20.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.18.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.17.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v8.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.