← Home

@casl/react

4
Versions
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

stalniy

Keywords

caslreactauthorizationaclpermissions

Accepted risks

Findings the reviewer chose to accept rather than block on.

SourceRuleReasonAccepted byWhen
provenance publisher-changed AI (provenance): Transition from stalniy to GitHub Actions CI/CD is documented by SLSA attestation; consistent with monorepo automation. ai
provenance missing-githead AI (provenance): CI/CD publish via GitHub Actions with SLSA provenance replaces gitHead as the source-commit link. ai
publish-pattern dormant-publish AI (publish-pattern): Long gap reflects real inactivity in this sub-package of the CASL monorepo, not account takeover; SLSA attestation corroborates legitimacy. ai

Versions (showing 4 of 4)

Version Deps Published
7.0.0 0 / 11
6.0.0 0 / 11
5.0.1 0 / 11
3.1.0 0 / 10

v7.0.0

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 Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

v5.0.1

3 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 Missing gitHead — previous versions had it provenance

[Accepted risk] This version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.

INFO Publisher changed: stalniy → GitHub Actions (on 2026-01-18) provenance

[Accepted risk] This version was published by a different npm account than previous versions on 2026-01-18. This could indicate a legitimate maintainer transition or an account compromise.