← Home

@stricli/core

npm Repository Homepage

Build complex CLIs with type safety and no dependencies

16
Versions
Apache-2.0
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures gitHead linked

Maintainers

bloomberg-ossbbgbuildermolisani

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
typosquat typosquat.levenshtein:cors AI (typosquat): @stricli/core is Bloomberg's legitimate CLI framework package; similarity to 'cors' is coincidental substring match on 'core' vs 'cors'. Not a typosquat. ai
bogus-package bogus-package AI (bogus-package): Scoped monorepo package from Bloomberg with SLSA provenance; short README and missing keywords are cosmetic issues, not spam indicators. ai

Versions (showing 16 of 16)

Version Deps Published
1.3.0 0 / 15
1.2.9 0 / 15
1.2.8 0 / 15
1.2.7 0 / 15
1.2.6 0 / 15
1.2.5 0 / 15
1.2.4 0 / 19
1.2.3 0 / 19
1.2.2 0 / 19
1.2.1 0 / 19
1.2.0 0 / 19
1.1.2 0 / 19
1.1.1 0 / 19
1.1.0 0 / 19
1.0.1 0 / 19
1.0.0 0 / 19

v1.3.0

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.2.9

1 finding
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

v1.1.2

2 findings
INFO Has SLSA provenance attestation provenance

Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.

INFO Publisher changed: molisani → bbgbuilder (on 2025-03-27, known maintainer) provenance

This version was published by a different npm account (bbgbuilder) than the most recent previously approved version (molisani) on 2025-03-27, but bbgbuilder is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.1.1

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.1.0

1 finding
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

v1.0.1

2 findings
LOW No provenance attestation provenance

Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.

INFO Publisher changed: bbgbuilder → molisani (on 2024-10-22, known maintainer) provenance

This version was published by a different npm account (molisani) than the most recent previously approved version (bbgbuilder) on 2024-10-22, but molisani is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.

v1.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.