@goldstack/template-backup-central
Template utilities for backup central
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:@goldstack/infra | AI (dependencies): Internal goldstack monorepo dependency; consistent with package's ecosystem context. | ai | |
| dependencies | unvetted-dep:@goldstack/infra-aws | AI (dependencies): Internal goldstack monorepo dependency; consistent with package's ecosystem context. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-package | AI (dependencies): Internal goldstack monorepo dependency; consistent with package's ecosystem context. | ai | |
| provenance | no-provenance | AI (provenance): Goldstack monorepo packages consistently lack provenance; not a meaningful risk signal for this publisher. | ai |
v0.1.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.