@planningcenter/core-automations
Display and manage core automations
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): Established internal org package; provenance absence is consistent across all versions. | ai | |
| license | uncommon-license:UNLICENSED | AI (license): Private org component; UNLICENSED is intentional and stable across all versions. | ai |
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 1.15.0 | 6 / 50 | |
| 1.14.1 | 6 / 50 | |
| 1.14.0 | 6 / 50 | |
| 1.13.9 | 6 / 50 | |
| 1.13.5 | 5 / 50 | |
| 1.13.4 | 5 / 50 | |
| 1.13.3 | 5 / 50 | |
| 1.12.1 | 5 / 50 | |
| 1.12.0 | 5 / 50 | |
| 1.11.1 | 5 / 50 | |
| 1.11.0 | 5 / 50 | |
| 1.10.0 | 5 / 50 |
v1.15.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.13.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.10.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.