@fireproof/core-cli
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Raw IP is a localhost default for local dev/test storage; not a network exfiltration risk. | ai | |
| phantom-deps | phantom-dep:multiformats | AI (phantom-deps): Declared dep used in config/build context; stable false positive for this monorepo package. | ai | |
| phantom-deps | phantom-dep:@fireproof/vendor | AI (phantom-deps): Same-org monorepo package; phantom-dep heuristic is a stable false positive here. | ai | |
| phantom-deps | phantom-dep:@typescript/native-preview | AI (phantom-deps): Referenced in config files; stable false positive for this build tooling package. | ai |
Versions (showing 24 of 24)
| Version | Deps | Published |
|---|---|---|
| 0.24.19 | 21 / 0 | |
| 0.24.16 | 21 / 0 | |
| 0.24.15 | 20 / 0 | |
| 0.24.14 | 20 / 0 | |
| 0.24.13 | 20 / 0 | |
| 0.24.12 | 20 / 0 | |
| 0.24.11 | 20 / 0 | |
| 0.24.10 | 20 / 0 | |
| 0.24.9 | 20 / 0 | |
| 0.24.8 | 20 / 0 | |
| 0.24.7 | 20 / 0 | |
| 0.24.0 | 20 / 0 | |
| 0.23.15 | 13 / 5 | |
| 0.23.14 | 12 / 5 | |
| 0.23.13 | 12 / 5 | |
| 0.23.11 | 12 / 5 | |
| 0.23.10 | 12 / 5 | |
| 0.23.8 | 12 / 5 | |
| 0.23.7 | 12 / 5 | |
| 0.23.6 | 12 / 5 | |
| 0.23.5 | 12 / 4 | |
| 0.23.3 | 13 / 3 | |
| 0.23.2 | 12 / 3 | |
| 0.23.1 | 12 / 3 |
v0.24.19
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.16
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.24.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.15
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.14
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.13
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.11
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.23.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.23.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.