@nsshunt/stsappframework
TODO
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 | no-provenance | AI (provenance): Established internal framework package; no provenance attestation is consistent across all versions. | ai | |
| dependencies | unvetted-dep:@types/on-headers | AI (dependencies): @types/on-headers is a DefinitelyTyped type-definition package; minimal attack surface, stable for this package. | ai | |
| phantom-deps | phantom-dep:@types/pidusage | AI (phantom-deps): @types/* packages are type-only declarations; not imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:@types/on-headers | AI (phantom-deps): @types/* packages are type-only declarations; not imported at runtime by design. | ai | |
| phantom-deps | phantom-dep:socket.io-adapter | AI (phantom-deps): Referenced in config files as documented; stable false positive for this package. | ai |
Versions (showing 72 of 72)
| Version | Deps | Published |
|---|---|---|
| 3.3.124 | 29 / 11 | |
| 3.3.123 | 29 / 11 | |
| 3.3.122 | 29 / 11 | |
| 3.3.121 | 29 / 11 | |
| 3.3.120 | 29 / 11 | |
| 3.3.119 | 29 / 11 | |
| 3.3.118 | 29 / 11 | |
| 3.3.117 | 29 / 11 | |
| 3.3.116 | 29 / 11 | |
| 3.3.115 | 29 / 11 | |
| 3.3.114 | 29 / 11 | |
| 3.3.113 | 29 / 11 | |
| 3.3.112 | 29 / 11 | |
| 3.3.111 | 29 / 11 | |
| 3.3.110 | 29 / 11 | |
| 3.3.109 | 29 / 11 | |
| 3.3.108 | 29 / 11 | |
| 3.3.107 | 29 / 11 | |
| 3.3.106 | 29 / 11 | |
| 3.3.105 | 29 / 11 | |
| 3.3.104 | 29 / 10 | |
| 3.3.103 | 30 / 10 | |
| 3.3.102 | 30 / 10 | |
| 3.3.101 | 30 / 10 | |
| 3.3.100 | 30 / 10 | |
| 3.3.99 | 30 / 10 | |
| 3.3.98 | 30 / 10 | |
| 3.3.97 | 30 / 10 | |
| 3.3.96 | 30 / 10 | |
| 3.3.95 | 30 / 10 | |
| 3.3.94 | 30 / 10 | |
| 3.3.93 | 30 / 10 | |
| 3.3.92 | 30 / 10 | |
| 3.3.91 | 30 / 10 | |
| 3.3.90 | 30 / 10 | |
| 3.3.89 | 30 / 10 | |
| 3.3.88 | 30 / 10 | |
| 3.3.87 | 30 / 10 | |
| 3.3.86 | 30 / 10 | |
| 3.3.85 | 30 / 10 | |
| 3.3.84 | 30 / 10 | |
| 3.3.83 | 30 / 10 | |
| 3.3.82 | 30 / 10 | |
| 3.3.81 | 30 / 10 | |
| 3.3.80 | 30 / 10 | |
| 3.3.76 | 29 / 10 | |
| 3.3.60 | 32 / 11 | |
| 3.3.58 | 32 / 11 | |
| 3.3.57 | 32 / 11 | |
| 3.3.56 | 32 / 11 | |
| 3.3.55 | 32 / 11 | |
| 3.3.54 | 32 / 12 | |
| 3.3.53 | 32 / 12 | |
| 3.3.52 | 32 / 12 | |
| 3.3.51 | 32 / 12 | |
| 3.3.50 | 32 / 12 | |
| 3.3.49 | 32 / 12 | |
| 3.3.48 | 32 / 12 | |
| 3.3.47 | 32 / 12 | |
| 3.3.46 | 32 / 12 | |
| 3.3.45 | 32 / 12 | |
| 3.3.44 | 32 / 12 | |
| 3.3.43 | 32 / 12 | |
| 3.3.42 | 32 / 12 | |
| 3.3.41 | 32 / 12 | |
| 3.3.40 | 32 / 12 | |
| 3.3.39 | 32 / 12 | |
| 3.3.38 | 32 / 12 | |
| 3.3.37 | 32 / 12 | |
| 3.3.36 | 32 / 13 | |
| 3.3.35 | 32 / 13 | |
| 3.3.34 | 32 / 13 |
v3.3.124
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.123
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.122
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.121
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.120
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.119
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.118
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.117
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.116
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.115
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.114
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.113
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.112
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.111
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.110
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.109
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.108
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.107
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.106
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.105
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.104
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.103
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.102
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.101
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.100
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.99
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.98
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.97
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.96
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.95
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.94
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.93
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.92
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.91
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.90
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.89
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.88
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.87
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.86
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.85
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.84
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.83
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.82
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.81
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.80
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.76
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.60
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.58
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.57
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.56
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.55
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.54
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.53
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.52
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.51
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.50
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.49
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.48
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.47
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.46
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.45
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.44
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.43
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.42
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.41
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.40
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.39
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.38
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.35
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v3.3.34
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.