travis-ci
node library to access the Travis-CI API
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from pwmckenna to ljharb is a documented legitimate handoff; ljharb is a highly trusted npm publisher with thousands of approved packages. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): ljharb is a well-known, highly reputable npm maintainer; this addition is consistent with a legitimate transfer. | ai | |
| phantom-deps | phantom-dep:underscore.string | AI (phantom-deps): underscore.string is declared in package.json dependencies; minor code quality issue, not a security concern for this package. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads a versioned bundled JSON routes file based on an API version config value — not arbitrary external module loading. Benign pattern stable across versions. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Published by ljharb, a highly trusted maintainer. Dormancy followed by routine maintenance publish with no material changes is not indicative of account takeover. | ai | |
| license | uncommon-license:BSD | AI (license): BSD is a well-known permissive open source license; the uncommon-license flag is a false positive for this package. | ai |
Versions (showing 15 of 15)
| Version | Deps | Published |
|---|---|---|
| 2.2.0 | 4 / 10 | |
| 2.1.1 | 4 / 10 | |
| 2.1.0 | 4 / 10 | |
| 2.0.3 | 4 / 10 | |
| 2.0.2 | 4 / 10 | |
| 2.0.0 | 4 / 10 | |
| 1.1.2 | 4 / 10 | |
| 1.1.0 | 4 / 8 | |
| 1.0.0 | 4 / 8 | |
| 0.1.4 | 4 / 8 | |
| 0.1.3 | 4 / 8 | |
| 0.1.2 | 4 / 8 | |
| 0.1.1 | 4 / 8 | |
| 0.1.0 | 4 / 8 | |
| 0.0.1 | 2 / 7 |
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
2 findingsThis version was published by a different npm account than previous versions on 2016-09-02. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.2
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. Consider requesting the maintainer enable provenance via CI/CD.