@salesforce/code-analyzer-regex-engine
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| maintainer-change | maintainer-added | AI (maintainer-change): Internal Salesforce team rotation on a trusted, high-volume publisher account. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Consistent with normal internal maintainer turnover, not a takeover pattern. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): isbinaryfile is a small, well-established utility; no install-time execution risk. | ai | |
| phantom-deps | phantom-dep:@types/node | AI (phantom-deps): Types package loaded by convention, not a real risk. | ai |
Versions (showing 37 of 37)
| Version | Deps | Published |
|---|---|---|
| 0.38.0 | 4 / 8 | |
| 0.37.0 | 4 / 8 | |
| 0.36.0 | 4 / 8 | |
| 0.35.0 | 4 / 8 | |
| 0.34.0 | 4 / 8 | |
| 0.33.0 | 4 / 8 | |
| 0.32.0 | 4 / 8 | |
| 0.31.0 | 4 / 8 | |
| 0.30.0 | 4 / 8 | |
| 0.29.0 | 4 / 8 | |
| 0.28.0 | 4 / 8 | |
| 0.27.0 | 4 / 8 | |
| 0.26.0 | 4 / 8 | |
| 0.25.0 | 4 / 8 | |
| 0.24.0 | 4 / 8 | |
| 0.23.0 | 4 / 8 | |
| 0.22.0 | 4 / 8 | |
| 0.21.0 | 3 / 8 | |
| 0.20.0 | 3 / 8 | |
| 0.19.0 | 3 / 8 | |
| 0.18.1 | 3 / 8 | |
| 0.18.0 | 3 / 8 | |
| 0.17.0 | 3 / 8 | |
| 0.16.2 | 3 / 8 | |
| 0.16.1 | 3 / 8 | |
| 0.15.0 | 3 / 8 | |
| 0.14.0 | 3 / 8 | |
| 0.13.0 | 3 / 8 | |
| 0.12.0 | 3 / 8 | |
| 0.11.1 | 3 / 8 | |
| 0.11.0 | 3 / 8 | |
| 0.10.0 | 3 / 8 | |
| 0.9.0 | 3 / 8 | |
| 0.8.2 | 3 / 8 | |
| 0.8.1 | 3 / 8 | |
| 0.8.0 | 2 / 8 | |
| 0.6.0 | 2 / 8 |
v0.38.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.22.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.21.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.14.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.6.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.