← Home

@alloy-js/csharp

npm Repository Homepage

Alloy components for CSharp language.

23
Versions
MIT
License
No
Install Scripts
Verified
Provenance

Supply chain provenance

Status for the latest visible version.

SLSA provenance attestation npm registry signatures No source commit

Maintainers

bterlson

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
publish-pattern new-deps-added AI (publish-pattern): New dep is `marked`, a well-known Markdown library; consistent with doc-generation use in this package. ai
phantom-deps phantom-dep:pathe AI (phantom-deps): pathe is a declared runtime dependency in package.json; phantom-dep heuristic misfires here. ai

Versions (showing 23 of 23)

Version Deps Published
0.24.0 5 / 11
0.23.0 5 / 10
0.22.0 5 / 10
0.20.0 4 / 7
0.19.0 4 / 7
0.18.0 4 / 7
0.17.0 3 / 7
0.16.0 3 / 7
0.15.0 3 / 7
0.14.0 3 / 7
0.13.0 3 / 7
0.12.0 3 / 7
0.11.0 3 / 7
0.10.0 3 / 9
0.9.0 3 / 9
0.8.0 3 / 9
0.7.0 3 / 9
0.6.0 3 / 9
0.5.0 3 / 9
0.4.0 3 / 9
0.3.0 3 / 9
0.2.0 3 / 9
0.1.0 3 / 9

v0.22.0

1 finding
LOW No provenance attestation provenance

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

v0.11.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.

v0.10.0

1 finding
LOW No provenance attestation provenance

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

v0.9.0

1 finding
LOW No provenance attestation provenance

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

v0.8.0

1 finding
LOW No provenance attestation provenance

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

v0.7.0

1 finding
LOW No provenance attestation provenance

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

v0.6.0

1 finding
LOW No provenance attestation provenance

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

v0.5.0

1 finding
LOW No provenance attestation provenance

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

v0.4.0

1 finding
LOW No provenance attestation provenance

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

v0.3.0

1 finding
LOW No provenance attestation provenance

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

v0.2.0

1 finding
LOW No provenance attestation provenance

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

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