@phosphor/application
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 | publisher-changed | AI (provenance): blink1073 (Steven Silvester) is a listed contributor in package.json and a long-standing trusted npm publisher with 3775 approved packages. This is a documented legitimate maintainer transition for the PhosphorJS ecosystem. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): blink1073 and phosphor-user are legitimate new maintainers as part of the known PhosphorJS project transition. blink1073 is already a listed contributor in package.json. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of 'phosphor' maintainer is consistent with the documented PhosphorJS project transition to blink1073/phosphor-user. No malicious indicators present. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by years; published by a highly trusted maintainer with strong track record. Absence of provenance is expected for this era of package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 1.7.3 | 3 / 14 | |
| 1.7.2 | 3 / 14 | |
| 1.7.1 | 3 / 14 | |
| 1.7.0 | 3 / 14 | |
| 1.6.4 | 3 / 14 | |
| 1.6.3 | 3 / 14 | |
| 1.6.2 | 3 / 14 | |
| 1.6.1 | 3 / 14 | |
| 1.6.0 | 3 / 3 | |
| 1.5.0 | 3 / 3 | |
| 1.4.0 | 3 / 3 | |
| 1.3.2 | 3 / 3 | |
| 1.3.1 | 3 / 3 | |
| 1.3.0 | 3 / 3 | |
| 1.2.0 | 3 / 3 | |
| 1.1.0 | 3 / 2 | |
| 1.0.1 | 3 / 2 | |
| 1.0.0 | 3 / 2 | |
| 0.3.1 | 3 / 2 | |
| 0.3.0 | 3 / 2 | |
| 0.2.0 | 3 / 2 | |
| 0.1.5 | 3 / 2 | |
| 0.1.4 | 3 / 2 | |
| 0.1.3 | 3 / 0 | |
| 0.1.2 | 3 / 0 | |
| 0.1.1 | 3 / 0 | |
| 0.1.0 | 3 / 0 |
v1.7.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.2
2 findingsThis version was published by a different npm account than previous versions on 2019-09-16. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
2 findingsThis version was published by a different npm account than previous versions on 2019-09-06. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.0
2 findingsThis version was published by a different npm account than previous versions on 2019-08-05. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
2 findingsThis version was published by a different npm account than previous versions on 2019-06-23. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
2 findingsThis version was published by a different npm account than previous versions on 2019-06-13. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
2 findingsThis version was published by a different npm account than previous versions on 2019-06-11. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
2 findingsThis version was published by a different npm account than previous versions on 2019-06-01. This could indicate a legitimate maintainer transition or an account compromise.
[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.0.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.1.2
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-02-21. This could indicate a legitimate maintainer transition or an account compromise.
v0.1.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.