@goldstack/template-user-management-cli
Command line tools for User Management template
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/utils-package-config | AI (dependencies): Same-org monorepo dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-cli | AI (dependencies): Same-org monorepo dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-log | AI (dependencies): Same-org monorepo dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-docker | AI (dependencies): Same-org monorepo dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-package | AI (dependencies): Same-org monorepo dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-template | AI (dependencies): Same-org monorepo dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-aws-lambda | AI (dependencies): Same-org monorepo dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@goldstack/infra | AI (dependencies): Same-org monorepo dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-sh | AI (dependencies): Same-org monorepo dependency; stable pattern across all versions of this package. | ai | |
| dependencies | unvetted-dep:@goldstack/infra-aws | AI (dependencies): Same-org monorepo dependency; stable pattern across all versions of this package. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-log | AI (phantom-deps): Same-org monorepo dep; phantom detection is a stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Established monorepo package; lack of Sigstore provenance is consistent across all 108 versions. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-sh | AI (phantom-deps): Same-org scoped package; may be used transitively or in build scripts. Stable FP. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-docker | AI (phantom-deps): Same-org scoped package; stable FP for this goldstack monorepo package. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-template | AI (phantom-deps): Same-org scoped package; stable FP for this goldstack monorepo package. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): source-map-support is a common runtime dep referenced in tsconfig/config files; stable false positive for this package. | ai |
Versions (showing 30 of 30)
| Version | Deps | Published |
|---|---|---|
| 0.1.111 | 15 / 10 | |
| 0.1.110 | 15 / 10 | |
| 0.1.108 | 15 / 10 | |
| 0.1.107 | 15 / 10 | |
| 0.1.106 | 15 / 10 | |
| 0.1.105 | 15 / 10 | |
| 0.1.103 | 15 / 10 | |
| 0.1.102 | 15 / 10 | |
| 0.1.101 | 15 / 10 | |
| 0.1.99 | 15 / 10 | |
| 0.1.98 | 15 / 10 | |
| 0.1.96 | 15 / 10 | |
| 0.1.92 | 15 / 10 | |
| 0.1.91 | 15 / 10 | |
| 0.1.89 | 15 / 10 | |
| 0.1.86 | 15 / 10 | |
| 0.1.83 | 15 / 11 | |
| 0.1.81 | 15 / 12 | |
| 0.1.75 | 15 / 12 | |
| 0.1.72 | 15 / 12 | |
| 0.1.71 | 15 / 12 | |
| 0.1.70 | 15 / 12 | |
| 0.1.68 | 15 / 12 | |
| 0.1.66 | 15 / 12 | |
| 0.1.65 | 15 / 12 | |
| 0.1.62 | 15 / 12 | |
| 0.1.61 | 15 / 12 | |
| 0.1.60 | 15 / 12 | |
| 0.1.59 | 15 / 12 | |
| 0.1.58 | 15 / 12 |
v0.1.111
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.108
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.107
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.106
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.103
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.102
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.101
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.99
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.98
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.96
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.92
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.91
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.89
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.86
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.83
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.81
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.75
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.72
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.71
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.70
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.68
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.66
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.65
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.62
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.61
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.59
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.58
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.