@univ-lehavre/atlas-crf-cli
CRF CLI - REDCap connectivity test and CRF server management
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): CLI tool in a university monorepo; sparse README and no keywords are cosmetic, not indicative of spam or malice. | ai | |
| phantom-deps | phantom-dep:@effect/sql | AI (phantom-deps): Effect ecosystem peer/transitive dep; declared for version pinning, not directly imported. | ai | |
| phantom-deps | phantom-dep:@effect/cluster | AI (phantom-deps): Effect ecosystem peer/transitive dep; declared for version pinning, not directly imported. | ai | |
| phantom-deps | phantom-dep:@effect/rpc | AI (phantom-deps): Effect ecosystem peer/transitive dep; declared for version pinning, not directly imported. | ai | |
| phantom-deps | phantom-dep:@effect/platform | AI (phantom-deps): Effect ecosystem peer/transitive dep; declared for version pinning, not directly imported. | ai | |
| phantom-deps | phantom-dep:@effect/printer-ansi | AI (phantom-deps): Effect ecosystem peer/transitive dep; declared for version pinning, not directly imported. | ai | |
| phantom-deps | phantom-dep:@effect/printer | AI (phantom-deps): Effect ecosystem peer/transitive dep; declared for version pinning, not directly imported. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 3.0.3 | 14 / 6 | |
| 3.0.0 | 14 / 6 | |
| 2.0.8 | 14 / 6 | |
| 2.0.7 | 14 / 6 | |
| 2.0.6 | 14 / 5 | |
| 2.0.5 | 14 / 5 | |
| 2.0.4 | 14 / 5 | |
| 2.0.3 | 14 / 5 | |
| 2.0.2 | 9 / 5 | |
| 2.0.1 | 9 / 5 | |
| 2.0.0 | 9 / 5 |
v3.0.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.