@live-change/access-control-service
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| semgrep | semgrep:eval-usage | AI (semgrep): eval() used to execute user-defined access-control functions stored in DB; intentional framework pattern, stable across versions. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 0.9.209 | 1 / 0 | |
| 0.9.208 | 1 / 0 | |
| 0.9.207 | 1 / 0 | |
| 0.9.206 | 1 / 0 | |
| 0.9.205 | 1 / 0 | |
| 0.9.204 | 1 / 0 | |
| 0.9.191 | 1 / 0 | |
| 0.9.176 | 1 / 0 | |
| 0.9.164 | 1 / 0 |
v0.9.209
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.208
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.207
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.206
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.205
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.191
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.176
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.9.164
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.