@firecms/cli
A CLI to perform FireCMS operations
4
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
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
gatti675
Keywords
clicreate-firecms-appfirecmsfirebasefirestorecmsreacttypescript
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| typosquat | typosquat.levenshtein:joi | AI (typosquat): @firecms/cli is a scoped CLI tool in the FireCMS ecosystem; Levenshtein match to 'joi' is a false positive. | ai | |
| semgrep | semgrep:base64-decode | AI (semgrep): Standard JWT payload decoding pattern; not obfuscation or malicious payload handling. | ai | |
| phantom-deps | phantom-dep:ws | AI (phantom-deps): Phantom dep heuristic; ws is a transitive/config-referenced dep, not a direct import concern. | ai | |
| phantom-deps | phantom-dep:pump | AI (phantom-deps): Phantom dep heuristic; pump is a transitive/config-referenced dep. | ai | |
| phantom-deps | phantom-dep:json5 | AI (phantom-deps): Phantom dep heuristic; json5 is a transitive/config-referenced dep. | ai | |
| phantom-deps | phantom-dep:nocache | AI (phantom-deps): Phantom dep heuristic; nocache is a transitive/config-referenced dep. | ai | |
| phantom-deps | phantom-dep:googleapis | AI (phantom-deps): Phantom dep heuristic; googleapis is a transitive/config-referenced dep for Firebase CLI tooling. | ai |
Versions (showing 4 of 4)
| Version | Deps | Published |
|---|---|---|
| 3.2.0 | 16 / 6 | |
| 3.1.0 | 16 / 6 | |
| 3.0.1 | 16 / 6 | |
| 3.0.0 | 16 / 6 |
v3.1.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.
v3.0.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.
v3.0.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.