director
A client Side/Server Side Router
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 (swaagie → jcrugzz) occurred in 2015 within the known nodejitsu/flatiron maintainer group. jcrugzz is a long-standing, well-vetted npm publisher. Stable for this package. | ai | |
| provenance | no-provenance | AI (provenance): Package was published in 2015, predating Sigstore provenance attestation. No provenance is expected and not a risk signal for this era of publication. | ai |
Versions (showing 28 of 28)
| Version | Deps | Published |
|---|---|---|
| 1.2.8 | 0 / 7 | |
| 1.2.7 | 0 / 7 | |
| 1.2.6 | 0 / 7 | |
| 1.2.5 | 0 / 7 | |
| 1.2.3 | 0 / 7 | |
| 1.2.2 | 0 / 7 | |
| 1.2.1 | 0 / 7 | |
| 1.2.0 | 0 / 7 | |
| 1.1.10 | 0 / 7 | |
| 1.1.9 | 0 / 7 | |
| 1.1.8 | 0 / 7 | |
| 1.1.7 | 0 / 7 | |
| 1.1.6 | 0 / 7 | |
| 1.1.4 | 0 / 7 | |
| 1.1.3 | 0 / 6 | |
| 1.1.2 | 0 / 5 | |
| 1.1.1 | 0 / 5 | |
| 1.1.0 | 0 / 5 | |
| 1.0.11 | 0 / 5 | |
| 1.0.10 | 0 / 5 | |
| 1.0.9 | 0 / 5 | |
| 1.0.8 | 0 / 6 | |
| 1.0.7 | 0 / 6 | |
| 1.0.6 | 1 / 6 | |
| 1.0.5 | 1 / 6 | |
| 1.0.4 | 1 / 5 | |
| 1.0.3 | 1 / 5 | |
| 1.0.2 | 1 / 5 |
v1.2.8
2 findingsThis version was published by a different npm account than previous versions on 2015-02-04. 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.
v1.2.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-12-16. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.6
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-12-16. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.5
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-12-06. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.3
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-02-28. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
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 2013-12-03. This could indicate a legitimate maintainer transition or an account compromise.
v1.2.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 2013-04-01. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.8
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 2012-11-12. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.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 2012-11-06. This could indicate a legitimate maintainer transition or an account compromise.
v1.1.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.11
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.10
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.5
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 2011-11-30. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.4
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 2011-11-28. This could indicate a legitimate maintainer transition or an account compromise.
v1.0.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.