@amsom-habitat/user-manager
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:axios | AI (phantom-deps): Runtime dependency in bundled library; declared and used correctly. | ai | |
| phantom-deps | phantom-dep:js-cookie | AI (phantom-deps): Runtime dependency in bundled library; declared and used correctly. | ai | |
| phantom-deps | phantom-dep:jwt-decode | AI (phantom-deps): Runtime dependency in bundled library; declared and used correctly. | ai | |
| phantom-deps | phantom-dep:@types/js-cookie | AI (phantom-deps): TypeScript types loaded by convention; stable for this package. | ai |
Versions (showing 32 of 32)
| Version | Deps | Published |
|---|---|---|
| 1.15.3 | 4 / 8 | |
| 1.15.2 | 4 / 8 | |
| 1.15.0 | 4 / 8 | |
| 1.13.0 | 4 / 8 | |
| 1.12.1 | 4 / 8 | |
| 1.12.0 | 4 / 8 | |
| 1.11.0 | 4 / 8 | |
| 1.10.0 | 4 / 8 | |
| 1.9.1 | 4 / 8 | |
| 1.9.0 | 4 / 8 | |
| 1.8.0 | 4 / 8 | |
| 1.7.0 | 4 / 8 | |
| 1.6.0 | 4 / 8 | |
| 1.5.7 | 4 / 8 | |
| 1.5.6 | 4 / 8 | |
| 1.5.5 | 4 / 8 | |
| 1.5.4 | 4 / 8 | |
| 1.5.3 | 4 / 8 | |
| 1.5.2 | 4 / 8 | |
| 1.5.1 | 4 / 8 | |
| 1.5.0 | 4 / 8 | |
| 1.4.0 | 4 / 8 | |
| 1.3.0 | 4 / 8 | |
| 1.1.8 | 2 / 5 | |
| 1.1.7 | 2 / 5 | |
| 1.1.6 | 2 / 5 | |
| 1.1.5 | 2 / 5 | |
| 1.1.4 | 2 / 5 | |
| 1.1.3 | 2 / 5 | |
| 1.1.1 | 2 / 5 | |
| 1.1.0 | 2 / 5 | |
| 1.0.0 | 2 / 5 |
v1.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.