@servicetitan/toolbelt-shared-registry
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 |
|---|---|---|---|---|
| provenance | no-provenance | AI (provenance): No provenance is consistent with this org's publishing pattern across 23 approved packages. | ai | |
| phantom-deps | phantom-dep:react | AI (phantom-deps): React is a peer dep; phantom-dep false positive for peer-only usage. | ai | |
| phantom-deps | phantom-dep:@servicetitan/log-service | AI (phantom-deps): Same-org dep; phantom-dep heuristic unreliable for indirect/re-exported usage. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Internal @servicetitan scoped package; missing metadata is typical for org-internal tooling, not spam. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Consistent with org-internal package pattern for @servicetitan scope. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 1.8.0 | 0 / 5 | |
| 1.7.5 | 0 / 5 | |
| 1.7.4 | 0 / 5 | |
| 1.7.3 | 0 / 5 | |
| 1.7.2 | 0 / 5 | |
| 1.7.1 | 0 / 4 | |
| 1.7.0 | 0 / 4 | |
| 1.6.0 | 0 / 4 | |
| 1.5.0 | 0 / 4 | |
| 1.4.0 | 0 / 4 | |
| 1.3.1 | 0 / 4 | |
| 1.3.0 | 4 / 1 | |
| 1.1.2 | 4 / 1 | |
| 1.1.1 | 4 / 1 | |
| 1.1.0 | 4 / 1 |
v1.8.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
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.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.