@planningcenter/tapestry
`@planningcenter/tapestry` is a library developed to provide tools to aid in designing Planning Center apps.
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@planningcenter/icons | AI (phantom-deps): Same-org dependency; declared but not directly imported is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): CI-published package with consistent release history; provenance absence is a process gap, not a security signal here. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): lodash is explicitly declared in dependencies; phantom-dep is a false positive for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 3.4.0 | 5 / 59 | |
| 3.3.1 | 5 / 59 | |
| 3.3.0 | 5 / 59 | |
| 3.2.2 | 5 / 55 | |
| 3.2.1 | 5 / 55 | |
| 3.2.0 | 5 / 55 | |
| 3.1.0 | 4 / 55 | |
| 3.0.1 | 4 / 55 | |
| 3.0.0 | 4 / 52 | |
| 2.10.1 | 4 / 51 | |
| 2.10.0 | 4 / 50 | |
| 2.9.0 | 4 / 50 | |
| 2.8.0 | 4 / 50 | |
| 2.7.0 | 4 / 50 | |
| 2.6.0 | 3 / 50 | |
| 2.5.0 | 3 / 50 |
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.9.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.
v2.8.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.
v2.7.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.6.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.
v2.5.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.