rsvp
A lightweight library that provides tools for organizing asynchronous code
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): All dynamic-require findings are in bower_components/mocha/mocha.js, a bundled dev/test artifact (mocha browser bundle). This is a well-known benign pattern in mocha's browser runner, not reachable by package consumers. | ai | |
| source-diff | net-exec-file:dist/test/browserify.js | AI (source-diff): Standard Browserify test bundle with module resolution boilerplate; not a dropper. Test artifacts are expected in dist/test/. | ai | |
| source-diff | source-size-tripled | AI (source-diff): Size increase from adding browserified test bundles (mocha, browserify, rsvp test files) under dist/test/. Normal build artifact growth. | ai | |
| provenance | publisher-changed | AI (provenance): fivetanley is a long-standing co-maintainer of rsvp (all 51 registry versions, first seen 4451 days ago). Legitimate maintainer, not a takeover. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by many years; no provenance is expected for this era of npm publishing. | ai |
Versions (showing 51 of 51)
| Version | Deps | Published |
|---|---|---|
| 4.8.5 | 0 / 27 | |
| 4.8.4 | 0 / 25 | |
| 4.8.3 | 0 / 25 | |
| 4.8.2 | 0 / 25 | |
| 4.8.1 | 0 / 25 | |
| 4.8.0 | 0 / 25 | |
| 4.7.0 | 0 / 26 | |
| 4.6.1 | 0 / 26 | |
| 4.0.2 | 0 / 26 | |
| 4.0.1 | 0 / 26 | |
| 4.0.0 | 0 / 26 | |
| 3.6.2 | 0 / 26 | |
| 3.6.1 | 0 / 26 | |
| 3.6.0 | 0 / 26 | |
| 3.5.0 | 0 / 15 | |
| 3.4.0 | 0 / 15 | |
| 3.3.3 | 0 / 15 | |
| 3.3.2 | 0 / 15 | |
| 3.3.1 | 0 / 15 | |
| 3.3.0 | 0 / 15 | |
| 3.2.1 | 0 / 18 | |
| 3.2.0 | 0 / 18 | |
| 3.1.0 | 0 / 20 | |
| 3.0.21 | 0 / 20 | |
| 3.0.20 | 0 / 20 | |
| 3.0.19 | 0 / 20 | |
| 3.0.18 | 0 / 20 | |
| 3.0.17 | 0 / 20 | |
| 3.0.16 | 0 / 24 | |
| 3.0.15 | 0 / 24 | |
| 3.0.14 | 0 / 22 | |
| 3.0.13 | 0 / 22 | |
| 3.0.12 | 0 / 20 | |
| 3.0.9 | 0 / 23 | |
| 3.0.8 | 1 / 23 | |
| 3.0.7 | 1 / 23 | |
| 3.0.6 | 0 / 23 | |
| 3.0.4 | 0 / 22 | |
| 3.0.3 | 0 / 22 | |
| 3.0.2 | 0 / 22 | |
| 3.0.1 | 0 / 22 | |
| 3.0.0 | 0 / 22 | |
| 2.0.4 | 0 / 8 | |
| 2.0.3 | 0 / 8 | |
| 2.0.2 | 0 / 8 | |
| 2.0.1 | 0 / 8 | |
| 2.0.0 | 0 / 7 | |
| 1.2.0 | 0 / 3 | |
| 1.1.1 | 0 / 3 | |
| 1.1.0 | 0 / 3 | |
| 1.0.0 | 0 / 1 |
v4.8.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.8.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2018-01-18. This could indicate a legitimate maintainer transition or an account compromise.
v4.7.0
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2017-10-03. This could indicate a legitimate maintainer transition or an account compromise.
v4.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.21
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.20
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.19
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.18
2 findingsThis version was published by a different npm account than previous versions on 2015-03-28. 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.
v3.0.17
2 findingsNewly added file contains both network calls and dynamic code execution. This is a hallmark of dropper/loader malware.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.16
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.15
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.14
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.13
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.12
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2014-08-08. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.7
2 findings[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2014-06-01. This could indicate a legitimate maintainer transition or an account compromise.
v3.0.6
2 findingsThis version was published by a different npm account than previous versions on 2014-02-19. 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.
v3.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.