@servicetitan/hammer-token
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 |
|---|---|---|---|---|
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used in a CLI utility (get-token.js) solely to open a browser for OAuth flow — standard pattern for Figma token retrieval tools, not a security risk. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal org package (@servicetitan) with 130 versions and 744 days history; missing repo/keywords/homepage is consistent across all versions and not a new risk signal. | ai |
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 3.0.2 | 0 / 6 | |
| 3.0.1 | 0 / 6 | |
| 3.0.0 | 0 / 6 | |
| 2.5.2 | 0 / 3 | |
| 2.5.1 | 0 / 3 | |
| 2.5.0 | 0 / 3 |
v3.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.