@goldstack/template-user-management
Template utilities for user management
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| publish-pattern | new-deps-added | AI (publish-pattern): New dep is the official AWS SDK Cognito client, directly aligned with this package's stated purpose. | ai | |
| dependencies | unvetted-dep:@goldstack/infra-aws | AI (dependencies): Same-org monorepo dependency; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@goldstack/infra | AI (dependencies): Same-org monorepo dependency; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-esbuild | AI (dependencies): Same-org monorepo dependency; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-template | AI (dependencies): Same-org monorepo dependency; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-package-config-embedded | AI (dependencies): Same-org monorepo dependency; stable false positive for this package family. | ai | |
| dependencies | unvetted-dep:@goldstack/utils-package | AI (dependencies): Same-org monorepo dependency; stable false positive for this package family. | ai | |
| phantom-deps | phantom-dep:source-map-support | AI (phantom-deps): source-map-support is a runtime dep listed in dependencies; phantom-dep heuristic false positive for this package. | ai | |
| phantom-deps | phantom-dep:@goldstack/utils-template | AI (phantom-deps): Same-org sibling dep; phantom-dep heuristic unreliable for monorepo packages. | ai |
Versions (showing 79 of 79)
| Version | Deps | Published |
|---|---|---|
| 0.2.10 | 10 / 10 | |
| 0.2.9 | 10 / 10 | |
| 0.2.8 | 10 / 10 | |
| 0.2.7 | 10 / 10 | |
| 0.2.6 | 10 / 10 | |
| 0.2.5 | 10 / 10 | |
| 0.2.2 | 10 / 10 | |
| 0.2.1 | 10 / 10 | |
| 0.1.92 | 10 / 10 | |
| 0.1.90 | 10 / 10 | |
| 0.1.89 | 10 / 10 | |
| 0.1.88 | 9 / 10 | |
| 0.1.87 | 9 / 10 | |
| 0.1.86 | 9 / 10 | |
| 0.1.85 | 9 / 10 | |
| 0.1.84 | 9 / 10 | |
| 0.1.83 | 9 / 10 | |
| 0.1.82 | 9 / 10 | |
| 0.1.81 | 9 / 10 | |
| 0.1.80 | 9 / 10 | |
| 0.1.78 | 9 / 10 | |
| 0.1.77 | 9 / 11 | |
| 0.1.75 | 9 / 12 | |
| 0.1.74 | 9 / 12 | |
| 0.1.73 | 9 / 12 | |
| 0.1.72 | 9 / 12 | |
| 0.1.71 | 9 / 12 | |
| 0.1.70 | 9 / 12 | |
| 0.1.69 | 9 / 12 | |
| 0.1.68 | 9 / 12 | |
| 0.1.67 | 9 / 12 | |
| 0.1.66 | 9 / 12 | |
| 0.1.65 | 9 / 12 | |
| 0.1.64 | 9 / 12 | |
| 0.1.63 | 9 / 12 | |
| 0.1.62 | 9 / 12 | |
| 0.1.61 | 9 / 12 | |
| 0.1.60 | 9 / 12 | |
| 0.1.59 | 9 / 12 | |
| 0.1.58 | 9 / 12 | |
| 0.1.57 | 9 / 12 | |
| 0.1.56 | 9 / 12 | |
| 0.1.55 | 9 / 12 | |
| 0.1.54 | 9 / 12 | |
| 0.1.53 | 9 / 12 | |
| 0.1.52 | 9 / 12 | |
| 0.1.51 | 9 / 12 | |
| 0.1.50 | 9 / 12 | |
| 0.1.49 | 9 / 12 | |
| 0.1.48 | 9 / 12 | |
| 0.1.47 | 9 / 12 | |
| 0.1.46 | 9 / 12 | |
| 0.1.45 | 9 / 12 | |
| 0.1.44 | 9 / 12 | |
| 0.1.43 | 9 / 12 | |
| 0.1.42 | 9 / 12 | |
| 0.1.41 | 9 / 12 | |
| 0.1.40 | 9 / 12 | |
| 0.1.39 | 9 / 12 | |
| 0.1.38 | 9 / 12 | |
| 0.1.37 | 9 / 12 | |
| 0.1.36 | 9 / 12 | |
| 0.1.35 | 9 / 12 | |
| 0.1.34 | 9 / 12 | |
| 0.1.33 | 9 / 12 | |
| 0.1.32 | 9 / 12 | |
| 0.1.31 | 9 / 12 | |
| 0.1.30 | 9 / 12 | |
| 0.1.29 | 9 / 12 | |
| 0.1.28 | 9 / 12 | |
| 0.1.27 | 9 / 12 | |
| 0.1.26 | 9 / 12 | |
| 0.1.25 | 9 / 12 | |
| 0.1.24 | 9 / 12 | |
| 0.1.23 | 9 / 12 | |
| 0.1.22 | 9 / 12 | |
| 0.1.21 | 9 / 12 | |
| 0.1.20 | 9 / 12 | |
| 0.1.19 | 9 / 12 |
v0.2.10
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.9
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.78
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.77
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.74
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.73
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.71
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.70
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.66
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.65
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.61
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.52
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.51
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.26
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.24
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.23
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.22
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.20
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.19
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.