@spinajs/reflection
SpinaJS reflection helpers
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 |
|---|---|---|---|---|
| publish-pattern | dormant-publish | AI (publish-pattern): Established spinajs org package with consistent publisher track record; 446 versions in registry supports legitimacy. | ai | |
| provenance | no-provenance | AI (provenance): Long-established @spinajs package; no provenance is consistent across all its versions. | ai | |
| phantom-deps | phantom-dep:@spinajs/log | AI (phantom-deps): Same-org transitive dep; phantom-dep heuristic fires on indirect usage, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@spinajs/configuration | AI (phantom-deps): Same-org transitive dep; phantom-dep heuristic fires on indirect usage, stable false positive for this package. | ai |
Versions (showing 7 of 107)
| Version | Deps | Published |
|---|---|---|
| 2.0.369 | 8 / 2 | |
| 2.0.368 | 8 / 2 | |
| 2.0.367 | 8 / 2 | |
| 2.0.363 | 8 / 2 | |
| 2.0.362 | 8 / 2 | |
| 2.0.361 | 8 / 2 | |
| 2.0.360 | 8 / 2 |
v2.0.369
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.368
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.367
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.363
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.362
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.361
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.360
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.