rhachet-brains-anthropic
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:helpful-errors | AI (phantom-deps): Declared runtime dep; likely used in compiled dist, heuristic false positive for this package. | ai | |
| npm-metadata | suspicious-initial-version | AI (npm-metadata): Publisher consistently uses 0.0.0 as initial version across their rhachet-* package ecosystem. | ai | |
| phantom-deps | phantom-dep:openai | AI (phantom-deps): Declared runtime dep; likely used in compiled dist, heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:wrapper-fns | AI (phantom-deps): Declared runtime dep; likely used in compiled dist, heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:type-fns | AI (phantom-deps): Declared in config files; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:domain-objects | AI (phantom-deps): Declared in config files; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:rhachet-artifact | AI (phantom-deps): Declared in config files; heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:rhachet-artifact-git | AI (phantom-deps): Declared in config files; heuristic false positive for this package. | ai |
Versions (showing 14 of 14)
| Version | Deps | Published |
|---|---|---|
| 0.4.1 | 10 / 28 | |
| 0.4.0 | 10 / 28 | |
| 0.3.3 | 10 / 28 | |
| 0.3.2 | 10 / 28 | |
| 0.3.1 | 10 / 28 | |
| 0.3.0 | 10 / 27 | |
| 0.2.2 | 9 / 27 | |
| 0.2.1 | 9 / 27 | |
| 0.2.0 | 9 / 27 | |
| 0.1.3 | 8 / 27 | |
| 0.1.2 | 8 / 27 | |
| 0.1.1 | 8 / 27 | |
| 0.1.0 | 8 / 27 | |
| 0.0.0 | 10 / 27 |
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.