@bildvitta/quasar-app-extension-asteroid
Asteroid
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed-stale | AI (provenance): Stale 940-day unremoved publish is inconsistent with takeover; legitimate transfer. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): Corresponds to same benign publisher transition. | ai | |
| publish-pattern | new-deps-added | AI (publish-pattern): execa and fontfaceobserver are well-known, benign packages. | ai | |
| semgrep | semgrep:dynamic-require | AI (semgrep): Dynamic require loads a user-supplied asteroid config file path; documented extension pattern, stable across versions. | ai | |
| phantom-deps | phantom-dep:execa | AI (phantom-deps): execa is explicitly declared as a direct dependency in package.json; phantom-dep is a false positive for this package. | ai |
Versions (showing 27 of 27)
| Version | Deps | Published |
|---|---|---|
| 3.19.0 | 9 / 0 | |
| 3.18.2 | 7 / 0 | |
| 3.18.1 | 7 / 0 | |
| 3.18.0 | 7 / 0 | |
| 3.17.0 | 7 / 0 | |
| 3.16.4 | 7 / 0 | |
| 3.16.3 | 7 / 0 | |
| 3.16.2 | 7 / 0 | |
| 3.16.1 | 7 / 0 | |
| 3.16.0 | 7 / 0 | |
| 3.15.0 | 7 / 0 | |
| 3.14.0 | 7 / 0 | |
| 3.13.1 | 5 / 0 | |
| 3.13.0 | 5 / 0 | |
| 3.12.0 | 5 / 0 | |
| 3.11.0 | 5 / 0 | |
| 3.10.0 | 3 / 0 | |
| 3.9.0 | 3 / 0 | |
| 3.8.0 | 3 / 0 | |
| 3.7.0 | 3 / 0 | |
| 3.6.0 | 3 / 0 | |
| 3.5.0 | 3 / 0 | |
| 3.4.0 | 3 / 0 | |
| 3.3.0 | 3 / 0 | |
| 3.2.0 | 3 / 0 | |
| 3.1.0 | 3 / 0 | |
| 3.0.0 | 2 / 0 |
v3.17.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.13.0
2 findingsThis version was published by a different npm account (gcarpi) than the most recent previously approved version (douglascalora) on 2023-12-27. It has since remained available on npm for 940 days without being unpublished, which is inconsistent with an account takeover — those are typically removed by npm shortly after discovery.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.